C-BLUE timing order and PlicoDM flat/setup support - #1
Open
mbonaglia wants to merge 1 commit into
Open
Conversation
Add hardware ROI/timing setup on PysilicoCamera with a short fps settle, clear-camera-dark support, and PlicoDM flat_cmd / zero_at_setup so bench YAMLs can configure DM and camera safely. Co-authored-by: Cursor <cursoragent@cursor.com>
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
2 participants
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.
Summary
PysilicoCamera.setupand exposure terminal updatesclear_camera_dark, and GPU-safe frame copyPlicoDMflat_cmd/zero_at_setupand fix EF→command path to usecpuArrayTest plan
im-calibYAML sets exposure/gain/fps without TT desync vs AFGflat_cmd_dataapplies flat at DM setup; modal poke adds on top of flatclear_camera_dark: truezeros pysilico dark so FITS dark subtraction is used alone