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-1162 Instrument control development <p>As it has an important effect on the data, we need to track this as mhs and FITS keyword.<br/> A command to declare a mask change is also necessary.</p> INSTRM-1162

add a command and keyword to declare DCB pupil mask size

Task Normal Done Done arnaud.lefur arnaud.lefur SPS Sun, 17 Jan 2021 18:46:20 +0000 Thu, 11 Feb 2021 15:27:46 +0000 Thu, 11 Feb 2021 15:27:46 +0000 ics_dcbActor 0 3 <p>I think that a new mask should probably change the pfsDesignId too.</p> <p>From a 2020-01-27 ICS phone con, we propose that the dcbActor itself generate two keywords, one describing the per-collimator masks and one describing the fiber bundles. And we agree that we should plan for a maximum of 12 (11?) collimators. e.g.:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>dcbMasks=changeMJD,mask1Name,mask2Name..mask12Name dcbBundles=changeMJD,bundle1Name,bundle2Name..bundle12Name </pre> </div></div> <p>I would prefer to split the date in another keyword if that's okay, say:<br/> dcbMasks=mask1Name,mask2Name..mask12Name<br/> dcbBundles=bundle1Name,bundle2Name..bundle12Name</p> <p>dcbConfigDate=changeMJD</p> <p>Sure. Makes sense. If you settle on something and make the actorkeys change first I can go ahead with the ccdActor changes. Not obvious to me whether we dump the mask and bundle keys directly to FITS and always include them. I think yes. Umm, W_DMSKnn and W_DBNDnn?</p> Blocks INSTRM-1164 Development Rank 0|02qpuc:i6001gr068fhw9qo4o0m9 Sprint SM1PD-2021 A 2 Story Points 1.0