[DAMD-138] Add AGCC filename format Created: 20/Oct/22 Updated: 13/Nov/22 Resolved: 13/Nov/22 |
|
| Status: | Done |
| Project: | Data Model |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | hassan | Assignee: | hassan |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||
| Sprint: | preEngRun08Nov | ||||||||||||||||||||||||
| Reviewers: | chyan | ||||||||||||||||||||||||
| Description |
|
As mentioned in the slack thread https://sumire-pfs.slack.com/archives/C9TDPMVHT/p1665843835236469, a format for AGCC files need to be agreed and added to datamodel.txt. Currently AGCC files are named based on date and time of the exposures. |
| Comments |
| Comment by hassan [ 27/Oct/22 ] |
|
On slack, Craig proposed the following convention:
agcc_{pfs_visit:06d}_{agc_exposure_id:08d}.fits
Where agc_exposure_id is a unique integer (monotonically increasing exposure by exposure). In order to implement this change as soon as possible, yuki.moritani and I propose that if there are no objections by the ICS/PFI telecon 2022-10-28, this proposal is accepted and will be implemented as part of |
| Comment by hassan [ 13/Nov/22 ] |
|
Merged to master. |
| Comment by hassan [ 13/Nov/22 ] |
|
There is a discussion on slack about whether the TABLEn HDU are optional, and whether an additional column for flag information is required. These will be the topics of a separate ticket. |