-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Add track overlap check #380
Conversation
Don't put permanent output into a tmp dir : Ran on NOV2921A, output https://icxc.cfa.harvard.edu/aspect/tmp/starcheck-pr380/starcheck.html#obsid45890. |
The description is too terse. Think of the PR description being something that external reviewers might quickly glance at, or more likely that we might view in 5 years. |
Can you copy/paste the relevant starcheck output into the description in case someone is viewing this without being on VPN? |
Ah. If we've decided we want the test outputs to be permanent that's fine. |
Or should the output just live in the PR? Maybe that is the most sustainable choice. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Description
Add track overlap check.
The PEA discards a readout window that overlaps with another window. Review of the guide star tracking data (for the agasc supplement update) from the NOV2921A schedule shows that a guide star was frequently lost due to overlap with another guide star window.
The existing spoiler checks in selection and review have prevented most overlapping stars from occurring, but the NOV2921A star selection shows that two selectable guide stars could be selected with the existing code within 35 arcsecs and have no starcheck warning. This PR adds a check that two tracked items (MON, FID, GUI, BOT) are not within 60 arcsecs.
Testing