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
Reproducibility in reading the ToO.ecsv ledger #393
Comments
Although the Main Survey ToO ledger exists, we have only used it to perform dedicated-like |
ah right, sorry I forgot about that TILE/FIBER type (even though you reminded it to me recently...) I should then apply this TIMESTAMP cut only if fiberassign/py/fiberassign/fba_launch_io.py Lines 1184 to 1186 in 802de4c
right? That should solve the issue with no action needed on your side? And a clarification: I m a bit confused by your message: there is only one ToO.ecsv file, right (in $DESI_SURVEYOPS/mtl/main/ToO/)? that file will contain TOO_TYPE=TILE or FIBER targets (though for now, only TILE are there). |
Correct, I think that if you only apply the
Everything you say in the above is correct (there is also a ToO ledger in |
ok perfect, thanks for the confirmation. |
This is addressed in the merged #394. |
The original pre-shutdown 2020 Main ToO.ecsv file (and SV3) do not have a TIMESTAMP column.
That is potentially problematic to rerun fiber assignment, as the ToO.ecsv file will evolve.
See desihub/desitarget#761.
The text was updated successfully, but these errors were encountered: