https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/DAMD-138 Data Model <p>As mentioned in the slack thread <a href="https://sumire-pfs.slack.com/archives/C9TDPMVHT/p1665843835236469" class="external-link" rel="nofollow">https://sumire-pfs.slack.com/archives/C9TDPMVHT/p1665843835236469</a>, a format for AGCC files need to be agreed and added to <tt>datamodel.txt</tt>. </p> <p>Currently AGCC files are named based on date and time of the exposures.</p> DAMD-138

Add AGCC filename format

Task Normal Done Done hassan hassan EngRun Thu, 20 Oct 2022 00:58:51 +0000 Sat, 12 Nov 2022 16:58:12 +0000 Sat, 12 Nov 2022 15:07:18 +0000 0 3 <p>On slack, Craig proposed the following convention:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> agcc_{pfs_visit:06d}_{agc_exposure_id:08d}.fits </pre> </div></div> <p>Where <tt>agc_exposure_id</tt> is a unique integer (monotonically increasing exposure by exposure).</p> <p>In order to implement this change as soon as possible, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=yuki.moritani" class="user-hover" rel="yuki.moritani">yuki.moritani</a> 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 <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1764" title="Rename AGCC image files" class="issue-link" data-issue-key="INSTRM-1764"><del>INSTRM-1764</del></a>.</p> <p>Merged to master.</p> <p>There is a discussion on slack about whether the <tt>TABLEn</tt> HDU are optional, and whether an additional column for flag information is required. These will be the topics of a separate ticket.</p> Blocks INSTRM-1764 Relates DAMD-29 DAMD-141 INSTRM-1006 Development Rank 0|02qpi8:i Reviewers chyan Sprint preEngRun08Nov Story Points 1.0