add dr1/survey/ops/surveyops/tags/1.0/

[weaverba137]

No description provided.

[weaverba137]

@sbailey, is the intention here to move $DESI_ROOT/survey/ops/surveyops/tags/1.0 to dr1, and then add hand-edited bits and pieces like the mtl directory, or to have dr1 be a fresh svn export of that tag?

[schlafly]

If I understand correctly, tags/1.0 goes through 20230112.
https://desi.lbl.gov/trac/browser/data/surveyops/tags/1.0
That's not the same as the DR1 end date. I don't really worry about exposing more information, but I wanted to be able to point some of my code to the appropriate tag to generate progress figures like this one:

[sbailey]

Unfortunately the structure of surveyops doesn't immediately fit with the concept of tags given the multiple use cases for it. Tag 1.0 represents the state of surveyops at the time we ran Iron, i.e. which tiles-specstatus.ecsv was used for determining whether a tile was "done" and should be included in the DR1 sample. But since Iron was run considerably after the DR1 cutoff date, both the MTLs and the other tile files continued to evolve. We could consider a different tag (for revision r1776?) to represent the state of MTLs and other tile files at the cutoff date (20220613). Or even a mis-mash tag of a custom branch that used the state of most files at the cutoff date, augmented with the updated tiles-specstatus.ecsv that was used for Iron.

[weaverba137]

Updating the status of surveyops/1.0 tag:

• A tag of that name exists in svn.
• $DESI_ROOT/survey/ops/surveyops/tags/1.0 exists.
• However, only the ops directory is defined. In comparison EDR had mtl, sv2 and sv3 directories in addition.
• The directory has not been moved into the public/dr1/survey tree.