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-82 Data Model <p>Following discussions about the AG frameID during the DRP telecon 2020-05-22: an approach is needed to store AG exposures for all 6 cameras, taking into the account that there may be more than 100 exposures per visit, in contrast to the MCS.</p> DAMD-82

AG FrameId Allocation

Task Normal Won't Fix Won't Fix cloomis hassan Fri, 29 May 2020 16:36:18 +0000 Mon, 4 Jan 2021 20:23:05 +0000 Fri, 7 Aug 2020 17:35:46 +0000 0 3 <p>At the telecon dedicated to AG on June 23/24 2020 ( <a href="https://sumire.pbworks.com/w/page/140496828/WG%204%20(AG)%20telecon%20on%2023-24%20June%202020" class="external-link" rel="nofollow">https://sumire.pbworks.com/w/page/140496828/WG%204%20(AG)%20telecon%20on%2023-24%20June%202020 )</a>, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=eric" class="user-hover" rel="eric">eric</a> suggested and we agreed on implementing multiple HDUs to pack as many exposures as we can, rather than limiting them below 100 where somebody might have to decide a selection of 100 exposures.</p> <p>Those will get pretty unwieldy, but that may be fine if they are only used for archiving and SMOKA/STARS are happy. 6 HDUs per AG exposure, so at 10s/exposure 540 HDUs for 15 minutes? </p> <p>If we agree that these are only for archiving I think this is fine.</p> <p>Issue description and comments merged with <a href="https://pfspipe.ipmu.jp/jira/browse/DAMD-2" title="AG image output to archive" class="issue-link" data-issue-key="DAMD-2">DAMD-2</a>.</p> Blocks INSTRM-1001 Duplicate DAMD-2 Relates DAMD-29 Development Rank 0|02qprn:m Sprint 2DDRP-2021 A