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

Considerations for new observation-activity state: scan #25

Open
danielczech opened this issue Oct 27, 2021 · 0 comments
Open

Considerations for new observation-activity state: scan #25

danielczech opened this issue Oct 27, 2021 · 0 comments

Comments

@danielczech
Copy link
Collaborator

For now I am treating the scan state in the same way as the track state: we wish to record data anytime the array is in either of these states. The scan state appears to refer to observations in which the array scans smoothly through changing RA and Dec values, as opposed to stop-and-stare observations at fixed RA and Dec (in the case of the track state).

As it stands, RA and DEC will update smoothly in the headers in the scan state. Are there any other considerations? Do we want to communicate to the processing nodes that the array is in the scan state or is the above sufficient?

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

No branches or pull requests

1 participant