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-619 Instrument control development <p>We did some tests with medium resolution grating this week, but ingest failed for the biases</p> <p> </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>2019-02-27 14:56:27.834Z cmds 20 Actor.py:499 new cmd: ingest filepath=/data/pfs/pfs/2019-02-27/PFLA01292114.fits 2019-02-27 14:56:27.835Z cmds 20 Actor.py:499 new cmd: detrend filepath=/data/pfs/pfs/2019-02-27/PFLA01292114.fits root INFO: Loading config overrride file '/opt/lsst/software/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/obs_pfs/c8f11eeeb3a5bdafc8f16fb33da301cab319a441/config/ingest.py' CameraMapper INFO: Loading exposure registry from /drp/m1/registry.sqlite3 ingest.parse WARN: Unable to find value for dataType (derived from IMAGETYP) ingest.parse WARN: Unable to find value for expTime (derived from EXPTIME) ingest.parse WARN: Unable to find value for dateObs (derived from DATE-OBS) ingest.parse WARN: Unable to find value for taiObs (derived from DATE-OBS) ingest.parse WARN: translate_field failed to translate field: IMAGETYP not found ingest.parse WARN: translate_date failed to translate dateObs: DATE-OBS not found ingest.parse WARN: translate_date failed to translate taiObs: DATE-OBS not found ingest WARN: Failed to ingest file /data/pfs/pfs/2019-02-27/PFLA01292114.fits: No locations for get: datasetType:raw_filename dataId:DataId(initialdata={'site': 'L', 'category': 'A', 'visit': 12921, 'filter': 'm', 'arm': 'm', 'spectrograph': 1, 'ccd': 1, 'pfsConfigId': 0, 'slitOffset': 0.0}, tag=set()) 2019-02-27 14:56:28.329Z cmds 20 CommandLink.py:121 &gt; 1 753 i text='None' 2019-02-27 14:56:28.329Z cmds 20 CommandLink.py:121 &gt; 1 753 : ingest=/data/pfs/pfs/2019-02-27/PFLA01292114.fits' 2019-02-27 14:56:28.341Z cmds 20 CommandLink.py:121 &gt; 1 754 f text="command failed: KeyError(\"Keyword 'DATE-OBS' not found.\",) at /opt/lsst/software/stack/python/miniconda3-4.3.21/lib/python3.6/site-packages/astropy/io/fits/header.py:1675"</pre> </div></div> <p>it looks like these keywords are missing for the biases image, so it may not be a DRP related issue</p> <p> </p> <p> </p> INSTRM-619

Ingest failed for medium resolution bias images

Bug Normal Done Done cloomis fmadec SM1 Wed, 27 Feb 2019 15:18:26 +0000 Wed, 6 Mar 2019 13:28:06 +0000 Wed, 6 Mar 2019 13:28:06 +0000 ics_ccdActor 0 3 <p>Confirmed.</p> <p>I made a test with B1:</p> <p>I've started ics_ccdActor:1.3.8 and took a bias, those keys are missing indeed.</p> <p>so, we're currently running 1.3.6, header is fine ( W_VISIT excepted)</p> <p>How hard would it be to use the same <tt>wipe</tt>, <tt>read exptype</tt> sequence used for arc/flat/object exposures for bias and dark exposures? I don't think that the <tt>bias</tt> and <tt>darks</tt> commands can work in the long run. Convenient in the lab, but not sustainable.</p> <p>The visitId would also be parsed in the read command ?</p> <p>Not hard, but that require a bit of refactoring.</p> <p> The carrot is that the caller (you) would always use the same mechanism to take all exposures: <tt>wipe</tt> followed by <tt>read exptype visit=NNN etc</tt>. One way or the other the <tt>visit</tt> must be passed in, since the ccdActor will not be able to know what visit to use.</p> <p>right, that's coherent.</p> <p>My only concern is about biases, is the command flow fast enough ? you might have a 0.05s dark instead.</p> <p>Merged at 9dfba69, tagged 1.3.9</p> Development Epic Link INSTRM-510 Rank 0|u000b4: