[DAMD-82] AG FrameId Allocation Created: 30/May/20  Updated: 05/Jan/21  Resolved: 08/Aug/20

Status: Won't Fix
Project: Data Model
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: hassan Assignee: cloomis
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks INSTRM-1001 agccActor saves FITS image of AG cameras Won't Fix
Duplicate
duplicates DAMD-2 AG image output to archive In Progress
Relates
relates to DAMD-29 Define AGCC files for display while g... Open
Sprint: 2DDRP-2021 A

 Description   

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.



 Comments   
Comment by naoyuki.tamura [ 07/Aug/20 ]

At the telecon dedicated to AG on June 23/24 2020 ( https://sumire.pbworks.com/w/page/140496828/WG%204%20(AG)%20telecon%20on%2023-24%20June%202020 ), eric 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.

Comment by cloomis [ 07/Aug/20 ]

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?

If we agree that these are only for archiving I think this is fine.

Comment by hassan [ 08/Aug/20 ]

Issue description and comments merged with DAMD-2.

Generated at Sat Feb 10 15:34:03 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.