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/INSTRM-522 Instrument control development <p>I'm pulling the header generation apart into smaller pieces. The time and frame cards should be generated by PFS and not Gen2 (we have better knowledge of exposure timing)</p> <p>I'll leave the routines in the gen2Actor for now, but they should be moved into tron_actorcore or pfs_utils.</p> <p>[ This is <em>not</em> required for MCS engineering. ]</p> INSTRM-522

Move date/time and frame card creation from gen2Actor into actorcore.

Task Normal Done Done cloomis cloomis FITS ICS MCS SPS Wed, 10 Oct 2018 18:18:53 +0000 Thu, 14 May 2020 12:04:29 +0000 Thu, 14 May 2020 07:58:34 +0000 ics_gen2Actor tron_actorcore 0 3 <p>This includes LST, etc.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=furu" class="user-hover" rel="furu">Hisanori Furusawa</a> Here is an example of what has been implemented for time cards and what I understand we should be generating. Before we commit to this, I'd like to re-ask a couple of clarifying questions just in case something has changed recently:</p> <ul class="alternate" type="square"> <li>Is UTC the only possible TIMESYS? No TAI?</li> <li>Can any of the time values contain both date and time?</li> </ul> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>TIMESYS = 'UTC' / Time System used in the header DATE-OBS= '2000-01-01' / [YMD] Observation start MJD-STR = 51544.0 / [d] MJD at exposure start UT-STR = '00:00:00.000' / [HMS] UT at exposure start HST-STR = '14:00:00.000' / [HMS] HST at exposure start LST-STR = '20:17:57.509' / [HMS] LST at exposure start MJD = 51544.00002894 / [d] MJD at mid-exposure UT = '00:00:02.500' / [HMS] UT at mid-exposure HST = '14:00:02.500' / [HMS] HST at mid-exposure LST = '20:18:00.016' / [HMS] LST at mid-exposure MJD-END = 51544.00005787 / [d] MJD at exposure end UT-END = '00:00:05.000' / [HMS] UT at exposure end HST-END = '14:00:05.000' / [HMS] HST at exposure end LST-END = '20:18:02.523' / [HMS] LST at exposure end </pre> </div></div> <p>Thank you <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>. I think the list is complete.<br/> The MJD-STR seems to have a value format that is different from the dictionary.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>MJD-STR = 51544.0 / [d] MJD at exposure start --&gt; F20.8 </pre> </div></div> <p>TIMESYS: in the current Subaru FITS rule, it should be 'UT'. The rule needs to be updated if TAI is really required. Also needs to check any impacts with the other systems like STARS and Gen2.</p> <p>I do not think the current time keywords allow to contain the date. Under the current scheme, if you want to put a timestamp for something, either you would define such an instrument-specific keyword containing both date and time, or identify the time based on a combination of what is given by TIMESYS (it's 'UTC' now, though) and the time string in the keyword.</p> <p>Unchanged since 2019-10-01 comment and revision af8dbf1. In tags 2.1.3 and later.</p> Blocks INSTRM-778 Duplicate INSTRM-704 Relates INSTRM-484 INSTRM-506 Development Rank 0|02qpuc:i6001gtpi8zx0k0109 Sprint SM1PD-2020 B SM1PD-2020 C SM1PD-2020 D SM1PD-2020 E Story Points 1.0