Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

reg_ref_frame use isn't caught by pipeline_precheck #410

Open
vreuter opened this issue Jan 17, 2025 · 0 comments
Open

reg_ref_frame use isn't caught by pipeline_precheck #410

vreuter opened this issue Jan 17, 2025 · 0 comments
Assignees
@vreuter
Labels
bug Something isn't working configuration likely solved
Milestone
v0.12

Comments

@vreuter
Copy link
Collaborator

vreuter commented Jan 17, 2025

The key for which timepoint to use as reference for drift correction was changed from reg_ref_frame to reg_ref_timepoint. This should be caught in the pipeline precheck, rather than causing an error in nuclei drift correction, when the value is accessed for the first time. Seen w/ @josephneos1010 in 6305.
@vreuter vreuter added bug Something isn't working configuration labels Jan 17, 2025
@vreuter vreuter added this to the v0.12 milestone Jan 17, 2025
@vreuter vreuter self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vreuter vreuter

Labels
bug Something isn't working configuration likely solved
Projects
None yet
Milestone
v0.12
Development

No branches or pull requests
1 participant
@vreuter