[PIPE2D-412] Make directory for pfsDesign files configurable Created: 30/Apr/19 Updated: 01/May/19 Resolved: 01/May/19 |
|
| Status: | Done |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | price | Assignee: | price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Reviewers: | fmadec |
| Description |
|
fmadec notes that their directories containing the images are not writable by ordinary users, so it's not easy to put a pfsDesign file in there. To make it easier, let's have the directory containing the pfsDesign files to be configurable. |
| Comments |
| Comment by price [ 30/Apr/19 ] |
|
fmadec, could you please verify that this works for you? pfs@76fda89da841:~/pfs/pipe2d-412 $ ls images/ PFFA00000011.fits@ PFFA00000812.fits@ PFFA00001711.fits@ PFFA00002512.fits@ PFFA00000012.fits@ PFFA00000911.fits@ PFFA00001712.fits@ PFFA00002611.fits@ PFFA00000111.fits@ PFFA00000912.fits@ PFFA00001811.fits@ PFFA00002612.fits@ PFFA00000112.fits@ PFFA00001011.fits@ PFFA00001812.fits@ PFFA00002711.fits@ PFFA00000211.fits@ PFFA00001012.fits@ PFFA00001911.fits@ PFFA00002712.fits@ PFFA00000212.fits@ PFFA00001111.fits@ PFFA00001912.fits@ PFFA00002811.fits@ PFFA00000311.fits@ PFFA00001112.fits@ PFFA00002011.fits@ PFFA00002812.fits@ PFFA00000312.fits@ PFFA00001211.fits@ PFFA00002012.fits@ PFFA00002911.fits@ PFFA00000411.fits@ PFFA00001212.fits@ PFFA00002111.fits@ PFFA00002912.fits@ PFFA00000412.fits@ PFFA00001311.fits@ PFFA00002112.fits@ PFFA00003011.fits@ PFFA00000511.fits@ PFFA00001312.fits@ PFFA00002211.fits@ PFFA00003012.fits@ PFFA00000512.fits@ PFFA00001411.fits@ PFFA00002212.fits@ PFFA00003111.fits@ PFFA00000611.fits@ PFFA00001412.fits@ PFFA00002311.fits@ PFFA00003112.fits@ PFFA00000612.fits@ PFFA00001511.fits@ PFFA00002312.fits@ PFFA00003211.fits@ PFFA00000711.fits@ PFFA00001512.fits@ PFFA00002411.fits@ PFFA00003212.fits@ PFFA00000712.fits@ PFFA00001611.fits@ PFFA00002412.fits@ PFFA00003311.fits@ PFFA00000811.fits@ PFFA00001612.fits@ PFFA00002511.fits@ PFFA00003312.fits@ pfs@76fda89da841:~/pfs/pipe2d-412 $ ls designs/ pfsConfig-0x0000000000000001-000000.fits@ pfsConfig-0x0000000000000001-000001.fits@ pfsConfig-0x0000000000000001-000002.fits@ pfsConfig-0x0000000000000001-000003.fits@ pfsConfig-0x0000000000000001-000004.fits@ pfsConfig-0x0000000000000001-000005.fits@ pfsConfig-0x0000000000000001-000006.fits@ pfsConfig-0x0000000000000001-000007.fits@ pfsConfig-0x0000000000000001-000008.fits@ pfsConfig-0x0000000000000001-000009.fits@ pfsConfig-0x0000000000000001-000010.fits@ pfsConfig-0x0000000000000001-000011.fits@ pfsConfig-0x0000000000000001-000012.fits@ pfsConfig-0x0000000000000001-000013.fits@ pfsConfig-0x0000000000000001-000014.fits@ pfsConfig-0x0000000000000001-000015.fits@ pfsConfig-0x0000000000000001-000016.fits@ pfsConfig-0x0000000000000001-000017.fits@ pfsConfig-0x0000000000000001-000018.fits@ pfsConfig-0x0000000000000001-000019.fits@ pfsConfig-0x0000000000000001-000020.fits@ pfsConfig-0x0000000000000001-000021.fits@ pfsConfig-0x0000000000000001-000022.fits@ pfsConfig-0x0000000000000001-000023.fits@ pfsConfig-0x0000000000000001-000024.fits@ pfsConfig-0x0000000000000001-000025.fits@ pfsConfig-0x0000000000000001-000026.fits@ pfsConfig-0x0000000000000001-000027.fits@ pfsConfig-0x0000000000000001-000028.fits@ pfsConfig-0x0000000000000001-000029.fits@ pfsConfig-0x0000000000000001-000030.fits@ pfsConfig-0x0000000000000001-000031.fits@ pfsConfig-0x0000000000000001-000032.fits@ pfsConfig-0x0000000000000002-000033.fits@ pfs@76fda89da841:~/pfs/pipe2d-412 $ mkdir repo pfs@76fda89da841:~/pfs/pipe2d-412 $ echo lsst.obs.pfs.PfsMapper > repo/_mapper pfs@76fda89da841:~/pfs/pipe2d-412 $ ingestPfsImages.py repo images/*.fits --pfsConfigDir designs/ CameraMapper INFO: Loading Posix exposure registry from /home/pfs/pfs/pipe2d-412/repo ingestPfs INFO: images/PFFA00000011.fits --<link>--> /home/pfs/pfs/pipe2d-412/repo/2019-03-22/PFFA000000b1.fits ingestPfs INFO: designs/pfsConfig-0x0000000000000001-000000.fits --<link>--> /home/pfs/pfs/pipe2d-412/repo/pfsConfig/2019-03-22/pfsConfig-0x0000000000000001-000000.fits [...] |
| Comment by fmadec [ 30/Apr/19 ] |
|
I will try tomorrow, I have a ssh connection issue right now. But if I may, do we need this ? I mean we have the fits keyword value, so I am not sure to understand why we need a pfsconfig file per config... Fabrice
|
| Comment by price [ 30/Apr/19 ] |
|
You wanted to be able to ingest pfsConfig/pfsDesign files from a separate directory from the raw data, right? |
| Comment by fmadec [ 30/Apr/19 ] |
|
right. Even if I tested that not using the correct way it works fine. Thanks Fabrice |
| Comment by price [ 01/May/19 ] |
|
Thanks, fmadec. Merged to master. |