Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
With DM-22955, spatially varying narrow-band filter information has been added to obs_subaru. These updated transmission curves need to be installed on lsst-dev in /datasets/hsc/repo and on tigress in /tigress/HSC/HSC in order to be used generally.
Installation of the transmission curves is described in RFC-440, and is simply:
setup obs_subaru
|
installTransmissionCurves.py /path/to/repo
|
Note that the above path is to the regular data repository root, not a calibRoot; transmission curves are not yet versioned (they will be in the Gen3 butler). This new installation could overwrite the old installation as it will install new spatially varying information, and the older data (g/r/r2/i/i2/z) has not changed. However, if that is undesirable, the old transmission directory could be moved to transmission_old.
As per our policy on modifications to /datasets:
- Description and reason for addition/change/deletion: The new datasets enable new processing steps that improve the quality of the reductions for narrow-band data.
- Target top-level-directory for location of addition/change/deletion: /datasets/hsc/repo
- Organization of data:
- transmission curves will go into /datasets/hsc/repo/transmission
- Other necessary domain knowledge as identified by project members relating to the contents of the data: provided in the RFC link above.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Remote Link | This issue links to "Page (Confluence)" [ 22968 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 23028 ] |
Hsin-Fang Chiang
made changes -
Is w_2020_04 new enough? Or will we need w_2020_05?
Hsin-Fang Chiang
added a comment - Is w_2020_04 new enough? Or will we need w_2020_05? I think this was in w_2020_02 or even earlier, but the changelog is down right now so I can't easily check. So w_2020_04 would be fine. I think I need to file an implementation ticket. Should this be to (a) create a directory that I can write to, or (b) for Hsin-Fang Chiang to run (assuming you have write access)?
Eli Rykoff If I understand correctly I can do this directly in /datasets/hsc/repo which I think I have the write access now.
I filed DM-23254 for myself; I'll check with you whether I get the command right.
Hsin-Fang Chiang
added a comment - Eli Rykoff If I understand correctly I can do this directly in /datasets/hsc/repo which I think I have the write access now.
I filed DM-23254 for myself; I'll check with you whether I get the command right. Adopted, with implementation on DM-23254
| Status | Proposed [ 10805 ] | Adopted [ 10806 ] |
Done for /datasets/hsc/repo
Maybe the Princeton HSC team can take care of /tigress/HSC/HSC ?
Hsin-Fang Chiang
added a comment - Done for /datasets/hsc/repo
Maybe the Princeton HSC team can take care of /tigress/HSC/HSC ? Paging John Swinbank
I am paged, but I don't really know anything about /tigress/HSC/HSC — all I do on Tiger is poke the shared stack occasionally. I'm happy to run the commands Hsin-Fang supplied in the RFC, but it might be wiser to get somebody who actually knows what they're doing (Paul Price?) to take care of it.
I've done /projects/HSC/HSC.
Paul Price
added a comment - I've done /projects/HSC/HSC . | Resolution | Done [ 10000 ] | |
| Status | Adopted [ 10806 ] | Implemented [ 11105 ] |
Thanks Paul!
| Remote Link | This issue links to "Page (Confluence)" [ 23101 ] |
This can now be adopted, and I think we may want to get it in before PDR2 processing starts.