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.

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 moon constraint to targets in fields.yaml #603

Open
fergusL opened this issue Sep 4, 2023 · 0 comments
Open

add moon constraint to targets in fields.yaml #603

fergusL opened this issue Sep 4, 2023 · 0 comments

Comments

@fergusL
Copy link
Contributor

fergusL commented Sep 4, 2023

At the moment we specify a one size fits all moon separation constraint that get used by the scheduler to veto any targets that are too close to the moon. We also have a problem where we want to observe some targets only when the moon is not up and others only when the moon is up.

If we add a minimum moon separation parameter to the observation config in the fields.yaml file we can specify moon separation>180?degrees and then pocs can prioritise dark time targets before the moon rises. Then when the moon has risen, those targets will be vetoed and pocs will start scheduling bright time targets. This mean we won't have to interrupt pocs in the middle of the night when the moon rises to switch target files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant