-
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
populate dr1/survey/fiberassign #33
Comments
In public/dr1/survey/fiberassign/ I created links to ../../../edr/survey/fiberassign/SV1/ and SV3/ . The equivalent SV2 link already existed. I also moved + linked the additional needed dates from survey/fiberassign/special/ -> public/dr1/survey/fiberassign/special/, created their checksums: 20210708, 20210918 20210919 20210923 20211030 20211228 20220120 20220324 .
Note that some of the files are of the form
|
@sbailey, at first reading, I think I understand what is needed. Also note, I am @weaverba137, not |
@sbailey, some, but not all of the |
Also, |
Other items after moving the files:
|
survey/fiberassign/main now has permissions set correctly and checksums. The remaining question has to do with differences in the data models for different surveys. |
For the data model, I suggest pragmatism:
It appears that more recent special/DATE started using the TILEGROUP concept such that survey/fiberassign/special/DATE/TILEGROUP is analogous to survey/fiberassign/main/TILEGROUP, while still using the DATE to group batches of special tiles. It just happens that special tiles are all in the 082nnn range and thus have the 082/ subdirectory as the TILEGROUP. These are archival in the sense that we want to keep them, albeit while being flexible about the evolving structure and needs of one-off special program planning. @weaverba137 please add the checksums. I think that is the last remaining data task for this ticket; the rest can be passed to desidatamodel, right? |
OK, that sounds like a good way to proceed.
Yes, I agree with that. |
I've added the missing checksums to the special directories and opened desihub/desidatamodel#206. |
No description provided.
The text was updated successfully, but these errors were encountered: