Add subframe geometry keywords and run exposures on a worker thread - #235
Merged
Merged
Conversation
# Conflicts: # daemons/generic/camera # src/hispec/driver/tracking_camera/keywords.py
prkrtg
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
subframemode,y0/y1/x0/x1,subframeheight/subframewidthandgeometrystatus. Bounds and sizes read in either mode; each is writable only in the mode that accepts it, and a rejected write names the keyword that does work thereexposeon a worker thread so it returns at once and progress shows instate; a secondexposeis refused while one runsabortinterrupt a run and settle to idle rather than error, and report the written path inlastframeonce the asynchronous writer has flushed