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

tools for when to rerun fiber assignment #18

Closed
sbailey opened this issue Mar 13, 2017 · 3 comments · Fixed by #66
Closed

tools for when to rerun fiber assignment #18

sbailey opened this issue Mar 13, 2017 · 3 comments · Fixed by #66
Milestone

Comments

@sbailey
Copy link
Contributor

sbailey commented Mar 13, 2017

Write new tools for determining which tiles are eligible for fiber assignment, i.e. all of the lower pass tiles that cover it have been observed and processed. Integrate the output of that with the inputs to fiber assignment. Another output of these tools is the list of tiles eligible for observing used as an input to afternoon planning described in #17 .

See DESI-2728 for a discussion of when fiber assignment should be rerun on what tiles and how that interacts with the survey strategy.

I'm assigning this ticket in desisurvey (not fiberassign) since this is a survey strategy choice, not the choice of fiber assignment itself.

@sbailey sbailey added this to the DC2017 Prep milestone Mar 13, 2017
@sbailey
Copy link
Contributor Author

sbailey commented Mar 14, 2017

Here is the state machine from DESI-2728 that the tools should help automate to assist the human survey coordinator. Note that some transitions are automatic, while others could be organized by the tools but the actual state transition is the survey coordinator's choice:

tilestate

@dkirkby
Copy link
Member

dkirkby commented Sep 26, 2017

Is it useful to keep this issue open? The state machine above is still valid except that now the right-most two boxes should be updated to reflect the monthly FA cadence.

@sbailey
Copy link
Contributor Author

sbailey commented Sep 28, 2017

Internally surveyplan knows which tiles should be fiber assigned, but it doesn't seem to dump that into a list for someone to use for actually doing fiber assignment. If that does exist, please point me to that. Or perhaps it is just a matter of needing documentation about the progress.fits file to know how to interpret the "status" column and some tools for parsing that as input for fiber assignment.

Related: We also appear to be missing the hooks for doing the human overrides to force or avoid observation. These should be separate files with just the overrides, not a human hand-editing the standard FITS file output to replace the automated progress report.

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

Successfully merging a pull request may close this issue.

2 participants