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

Consider not processing the first image after mechanism moves finishes #362

Open
bberkeyU opened this issue Dec 6, 2023 · 0 comments
Open

Consider not processing the first image after mechanism moves finishes #362

bberkeyU opened this issue Dec 6, 2023 · 0 comments
Assignees
@mgalloy
Labels
enhancement new feature questions coding is stoppped to determine correct path
Milestone
KCor 2.2

Comments

@bberkeyU
Copy link
Collaborator

bberkeyU commented Dec 6, 2023 •
edited by mgalloy

We see some bright light patterns assoicated with the cover moving out of the beam in 20220902_222740_kcor.fts.gz which reports cover out. The pattern is considerably fainter than the image before in which the cover is mid.

Most of the image is ok, but the SE is funky; so the team should decide if it is worth excluding the cover (and probally diffuser/polarizer) edge case images.
@bberkeyU bberkeyU added enhancement new feature questions coding is stoppped to determine correct path labels Dec 6, 2023
@mgalloy mgalloy changed the title Consider not processing the first image after mechanism moves finishes. Consider not processing the first image after mechanism moves finishes Dec 6, 2023
@mgalloy mgalloy added this to the 2.2 reprocessing milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mgalloy mgalloy

Labels
enhancement new feature questions coding is stoppped to determine correct path
Projects
None yet
Milestone
KCor 2.2
Development

No branches or pull requests
2 participants
@mgalloy @bberkeyU