desihub / desida Goto Github PK

Based on discussion with @sbailey:

1. The "original" files that are now in (guadalupe|iron)/zcatalog/v0 have actually been modified by the addition of the ZCATVER header keyword.
2. The really original files still exist on HPSS in HTAR files that should be renamed.

So the procedure will be:

• Create new checksum files for (guadalupe|iron)/zcatalog/v[01].
• Rename really original tape backups of zcatalog.
• Create tape backups for (guadalupe|iron)/zcatalog/v[01].
• Update the top-level inventory-(guadalupe|iron).txt files.
• Update checksums of top-level files.
• Redo tape backups of top-level files.

Ensure all links are updated.

Draft directory:/global/cfs/cdirs/desi/users/abrodze/QSOredshiftsY1/zlya-QSO-DR1-v0
1 catalog file, 3 files total

Initial Checks:

• Includes README
• Columns in ALLCAPS
• Extension names in ALLCAPS
• Files include units

Initial Notes:

• Can you draft a short (~1-2 paragraph) summary of the VAC to include in the DR1 paper? For an example of what this would look like you can look at section 3.3.6 of the EDR paper (https://arxiv.org/abs/2306.06308).
• It looks like you have an .ipynb_checkpoints folder in your VAC directory, unless we need it I think we should delete it
• If possible can you propagate the degree units to the catalog (as outlined in the README)?
• No comments on the README at this time except to include paper links when they're available, although in the near future it'll need to be reformatted to match desidatadocs.

Draft directory: /global/cfs/cdirs/desi/users/hrincon/DESIVAST_V1
24 catalog files, 25 total

Initial Checks:

• Includes README
• Columns in ALLCAPS
• Extension names in ALLCAPS
• Files include units

Initial Notes:

• Your FITS files don't have EXTNAMEs, could you please add some to make it easier to access the table by EXTNAME instead of indices?
• Generally we request that FITS files include column units. You do have the units documented in the README, would it be possible to also propagate those to the fits files themselves?
• Can you draft a short (~1-2 paragraph) summary of the VAC to include in the DR1 paper? For an example of what this would look like you can look at section 3.3.6 of the EDR paper (https://arxiv.org/abs/2306.06308).

Draft directory:/global/cfs/cdirs/desi/users/pzw/v1
1 catalog file, 2 files total

Initial Checks:

• Includes README
• Columns in ALLCAPS
• Extension names in ALLCAPS
• Files include units

Initial Notes:

• The extension name "Bhmass" is not all caps, please update it
• Please include units in both the VAC file as well as the README file.
• What's the version number on your catalog? The file is labeled v1.1, but the directory level is v1, we should pick one so that they're consistent.
• No comments on the README at this time, although this might change at a later date.

Assign or co-assign to DR1 VAC coordinator.

Draft directory:/global/cfs/cdirs/desicollab/users/lucasnap/MgII-Absorber-Catalog-DR1/1.0
2 catalog files, 3 files total

Initial Checks:

• Includes README
• Columns in ALLCAPS
• Extension names in ALLCAPS
• Files include units

Initial Notes:

• Can you draft a short (~1-2 paragraph) summary of the VAC to include in the DR1 paper? For an example of what this would look like you can look at section 3.3.6 of the EDR paper (https://arxiv.org/abs/2306.06308).
• Since this looks like just an updated version of the EDR Vac, can you confirm this? If so I'm not sure much of this will be necessary to update and we'll be able to get away with probably not doing much on this one.

Ensure all links in the file are updated.