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-572 Instrument control development <p>The 2d pipeline expects to match science exposures to their flat and arc calibration exposures using their common pfsConfigId.</p> <p>But when taking odd and even fiber quartz exposures, half the cobras will be behind the spots so the actual configId will be wrong. </p> <p>Either lie about the configId, or, almost certainly better, include a card with the configId for the full field. Oh, `W_PFIDFL` or something equally ncmprhnsbl. </p> INSTRM-572

Track "real" pfsConfigId when taking odd and even quartz flats.

Task Normal Open Unresolved Unassigned cloomis PFI SPS Fri, 16 Nov 2018 21:41:23 +0000 Thu, 12 Aug 2021 23:56:07 +0000 0 3 <p>I'm not sure that the premise of this ticket is correct. We build flats and traces from odd/even flats <b>and then declare them to be valid in the calibration database</b>.  So the lookup is done via visit or equivalently time stamp, not via <tt>pfsConfigId</tt>.  I was expecting the cobra config to take even/odd spots to have different <tt>pfsDesignID</tt> s (and different <tt>pfsConfigID</tt> s too)</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>: I think we can close this ticket as 'wont fix', correct? It no longer makes sense as we have the <tt>FiberStatus.BLACKSPOT</tt> enumeration available in PfsConfigs.</p> Development Rank 0|s001s0: