Add ROI logic to i04 beam centre device#1799
Conversation
* Proof of concept device manager * Use fixtures parameter instead of **kwargs * Expand dependencies * Pre-optional handling * 'Working' optional dependencies * Docs, comments and warnings * Check for positional only arguments * Handle connections and support new loader in cli * Convert adsim to new loading * Add auto_connect to device manager * Remove references to connecting from device manager * DeviceResult wrappers * Demo adsim * build_and_connect method * Multiple manager CLI * FIXTUEES * Use device decorator for timeouts * Type build_and_connect and rely on fixtures for path provider * mostly reformatting * Make fixture generators lazy * Apologise for build_order method * Return function from fixture decorator * Add timeout parameter to build_and_connect * Remove dead comment * Use set in expand_dependencies to prevent repetition * Check for duplicate factory names * Add Ophyd v1 support * Connect Ophyd v1 devices * Move device_manager to new module Instead of burying it amongst the beamlines. * Remove test code from device_manager module * Remove debugging and commented code * Merge connectionspec and connectionparameters * Add or_raise method to DeviceBuildResult * Add docstrings * Use or_raise to handle build errors * Only set device name if required * Add TODOs to remove v1 support * Make v1 device timeout configurable * Default to waiting for v1 device connection * Add repr to v1 device factory * Split DeviceBuildResult devices and connection specs Makes access to the devices easier and makes it easier to build parameters * Remove device_type property from factories * Include fixture overrides in built devices * Fix duplication in factory repr * Add initial device_manager tests * Revert adsim changes for now * Enough tests to get full coverage Maybe enough tests to cover basic use * Create DeviceManager in fixture * Add test for docstrings * Reformat tests * Linting et al * Support single device manager name in CLI * Ignore mock type warnings * Appease pre-commit lints * Add tests for device manager use in CLI * Make 'devices' default name for device manager in CLI * Clean up TODO comments * Set return_value when creating mocks * Fix typing in v1_init decorator * Use ParamSpec when passing through __call__ * Handle or ignore var args * Update tests * Rename ignore skip test * Simplify LazyFixture __getitem__ * Used UserDict as base class for LazyFixtures * Make pyright happy * Remove need for type ignore --------- Co-authored-by: Robert Tuck <robert.tuck@diamond.ac.uk>
* Eiger changes from i04 beamline * Add test for two eiger stops being called at the same time * Revert async arming changes * Fix tests --------- Co-authored-by: Dominic Oram <dominic.oram@diamond.ac.uk>
* first try * add trigger function which writes to soft signals * small changes * get rid of max pixel location * add tests - need modifying as made with copilot * make triggerable for blesky plan * start to add max-pixel device in i04 (WIP because on beamline) * Finish adding device to i04.py * Add changes from beamline testing - from github * add comment for kernal size * attemt own tests * add my tests * add assert called onece tests * make changes from Dom's comments * add greyscale test * remove print statements in test * Fix merge issue --------- Co-authored-by: Dominic Oram <dominic.oram@diamond.ac.uk>
…n as the max pixel device (to blur and convert to greyscale)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1799 +/- ##
=======================================
Coverage 99.05% 99.05%
=======================================
Files 289 289
Lines 11000 11020 +20
=======================================
+ Hits 10896 10916 +20
Misses 104 104 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
olliesilvester
left a comment
There was a problem hiding this comment.
Great thanks! I can't actually approve this as it's my own PR but otherwise I would. Just a few comments.
Discussed in person: We might want to add an option in the plan to specify which zoom levels we want to use ROI for, but it's probably fine to always use it. Also, it would be good to properly close off this bit of work for now
|
|
||
| # Clip coordinates to stay within bounds | ||
| x_min = max(round_half_up(centre_x - x_dist), 0) | ||
| x_max = min(round_half_up(centre_x + x_dist), width) - 1 |
There was a problem hiding this comment.
what's the -1 for? Do we need it given that we do a +1 again on line 91?
There was a problem hiding this comment.
Yeah the -1 is just so x_min and x_max are semantically the same, i.e the min/max pixel included in the ROI array. I agree it's a bit weird given we have the +1 later on, but the alternative is returning
(x_max - 1, y_max - 1) for the bottom right corner coord of the box, which I think is more confusing.
| int, f"{prefix}OVER:{overlay_channel}:CenterY" | ||
| ) | ||
|
|
||
| self.roi_box_size = soft_signal_rw(int, 300) |
There was a problem hiding this comment.
Does this need to be a soft signal, maybe it's better just as an attribute?
There was a problem hiding this comment.
Not sure of the pros/cons of either tbh, happy to change it?
There was a problem hiding this comment.
Ah it's fine as-is
|
CI test failure looks unrelated, but linting is related. I will fix linting |
jacob720
left a comment
There was a problem hiding this comment.
Approved as Ollie's not allowed to
Adds ROI logic to beam centre device. Should fix issues we were seeing at zoom level 1.0
This was done by @srishtysajeev - I'm making a draft PR so MX daq remember to finish it off
Checks for reviewer
dodal connect ${BEAMLINE}