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/PIPE2D-1335 DRP 2-D Pipeline <p>Please make a plan for the data acquisition in December 2023 run. This is the first case to take a complete set of calibration data for all spectrograph (except for n4).</p> <p><b>The goal of the run</b></p> <p>    Take calibration data as much as possible to resolve the problems and improve the pipeline. Since we have all spectrographs and cameras (except for n4), try to define a standard set of data and the way to take (and reduce) in the regular operation.</p> <p><b>The data set we take</b> (<font color="#ff0000">PRELIMINARY!!</font>) Most of them below may be replaced by just a reference to the document of the standard data set we routinely take in future.</p> <p><b><span class="error">&#91;Higher priority&#93;</span></b></p> <ul class="alternate" type="square"> <li><b>biases / darks (~20 / ~140 min.)</b> <ul> <li>no telescope time needed</li> <li>masterBiases (20 min.?) and masterDarks (140 min.?) but take n-band darks occasionally for removing persistence</li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for detectorMap (~120 min.)</b> <ul> <li>a full set of arcs and quartz (configuration in <b>allHome</b>) <ul> <li>brn (5 frames per arc lamp and quartz) (60 min.?)</li> <li>bmn (5 frames per arc lamp and quartz) (80 min.?)</li> </ul> </li> <li>retake a few times during the run to see the stability (is this needed?)</li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for FiberProfiles (TBD min.)</b> <ul> <li>repeat the following sequence for <span class="error">&#91;*mod4+1, mod4+2, mod4+3, mod4+4*&#93;</span></li> </ul> </li> </ul> <ul> <li> <ul> <li> <ul> <li> (darkRoach) <ul> <li>configure to <b>allHidden</b> (20 min.)</li> <li>45 sec. quartz <b>brn for dithers of 0.0, -0.4, 0.2, 0.0, 0.2, 0.4, 0.0 pixels</b> (TBD min.)</li> <li>45 sec. quartz <b>bmn for dithers of 0.0, -0.4, 0.2, 0.0, 0.2, 0.4, 0.0 pixels</b> (TBD min.)</li> </ul> </li> <li>(mod4+x) <ul> <li>configure to <b>mod4+x</b> (2 min?)</li> <li>45 sec. quartz <b>brn for dithers of 0.0, -0.4, 0.2, 0.0, 0.2, 0.4, 0.0 pixels</b> (TBD min.)</li> <li>45 sec. quartz <b>bmn for dithers of 0.0, -0.4, 0.2, 0.0, 0.2, 0.4, 0.0 pixels</b> (TBD min.)</li> </ul> </li> </ul> </li> <li>We may add the sequence for <b>mod32</b> (or <b>mod16</b>) with no dithering in the above</li> <li>take n-band dark while configuring allHidden?</li> <li>can we replace bmn --&gt; m?**</li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for illumination study (TBD min.)</b> <ul> <li>take arc/quartz with/without flat screen (in <b>allHome)</b> <ul> <li>configure to <b>allHome</b> (if home keep the configuration)</li> <li>(with flat screen) <ul> <li>remove top screen (if removed keep the screen position)</li> <li>brn (3 frames for HgCd <span class="error">&#91;TBC&#93;</span> and quartz) </li> <li>bmn (3 frames for HgCd <span class="error">&#91;TBC&#93;</span> and quartz)</li> </ul> </li> <li>(without flat screen) <ul> <li>insert top screen</li> <li>brn (3 frames for HgCd <span class="error">&#91;TBC&#93;</span> and quartz) </li> <li>bmn (3 frames for HgCd <span class="error">&#91;TBC&#93;</span> and quartz)</li> </ul> </li> </ul> </li> <li>change illumination using different ring lamp position (in <b>allHome)</b> <ul> <li>configure to <b>allHome</b> (if home keep the configuration)</li> <li>repeat the following the lamp position in <span class="error">&#91;p1, p2, p3, p4&#93;</span> <ul> <li>Turn ring lamp p1</li> <li>brn, 3 repeats of TBD sec. ring lamp quartz (TBD min.)</li> <li>bmn, 3 repeats of TBD sec. ring lamp quartz (TBD min.)</li> </ul> </li> </ul> </li> </ul> </li> </ul> <p><b><span class="error">&#91;Lower priority&#93;</span></b></p> <ul class="alternate" type="square"> <li><b>data for background study (TBD min.)</b> <ul> <li>take sparse sky in <span class="error">&#91;*allHidden, mod32, mod16*&#93;</span> <ul> <li>configure to <b>allHidden</b> (20 min.)</li> <li>brn, 3 repeats of TBD sec. sky (TBD min)</li> <li>bmn, 3 repeats of TBD sec. sky (TBD min.)</li> <li>configure to <b>mod32</b> (2 min?)</li> <li>brn, 3 repeats of TBD sec. sky (TBD min)</li> <li>bmn, 3 repeats of TBD sec. sky (TBD min.)</li> <li>configure to <b>mod16</b> (2 min?)</li> <li>brn, 3 repeats of TBD sec. sky (TBD min)</li> <li>bmn, 3 repeats of TBD sec. sky (TBD min.)  </li> </ul> </li> <li>take arc/quartz in <span class="error">&#91;*allHidden, mod32, mod16?*&#93;</span> <ul> <li>configure to <b>allHidden</b> (20 min.)</li> <li>brn, 3 repeats of arcs and quartz (36 min)</li> <li>bmn, 3 repeats of arcs and quartz (48 min.)</li> <li>configure to <b>mod32</b> (2 min?)</li> <li>brn, 3 repeats of arcs and quartz (36 min)</li> <li>bmn, 3 repeats of arcs and quartz (48 min.)</li> <li>configure to <b>mod16</b> (2 min?) &lt;-- do we need?</li> <li>brn, 3 repeats of arcs and quartz (36 min)</li> <li>bmn, 3 repeats of arcs and quartz (48 min.)</li> </ul> </li> <li>do we need take allHidden data just before each brn(or bmn) sequence like fiberProfiles data?</li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for dot penumbra study (TBD min.)</b> <ul> <li>configure cobras at different distance from dots</li> <li>take brn, 3 repeats of quartz</li> <li></li> </ul> </li> <li><b>data for uniformity (~90 min.)</b> <ul> <li>quartz (in <b>allHome)</b> <ul> <li>configure to <b>allHome</b></li> <li>brn, 3 repeats of 60 sec. quartz, InR = -150,-90,-30,0,30,90,150 (7 min. x 7)</li> </ul> </li> <li> twilight (in <b>allHome)</b> <ul> <li>configure to <b>allHome</b></li> <li>brn, 3 repeats of 180 sec. twilight, InR = -90, 0, 90 (13 min. x 3)</li> </ul> </li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for PSF modeling (TBD min.)</b> <ul> <li>change various theta/phi angle <ul> <li>configure cobras at different theta/phi angle</li> <li>take brn, 3 repeats of quartz</li> </ul> </li> <li>(defocus data for Kota’s study if we have time)</li> </ul> </li> </ul> <ul class="alternate" type="square"> <li><b>data for n-band specific?</b></li> </ul> <p><b>Data analysis plan</b></p> <ul> <li>Generate CALIBs (a good chance for NAOJ to make CALIBs) <ul> <li>masterBiases/masterDarks --&gt; constructPfsBias.py &amp; constructPfsDark.py</li> <li>detectorMap --&gt; reduceArc</li> <li>fiberProfiles --&gt; reduceProfiles</li> <li>flat --&gt; TBC</li> </ul> </li> <li>QA analysis  <ul> <li>run detectorMapQA (based on Wilfred's notebook?)</li> <li>run extractionQA (Hamano-san will prepare a script)</li> </ul> </li> </ul> PIPE2D-1335

Plan for data acquisition for December 2023 run

Task Normal Done Done Kiyoto Yabe Kiyoto Yabe EngRun Tue, 28 Nov 2023 03:03:46 +0000 Wed, 24 Jan 2024 06:20:22 +0000 Fri, 19 Jan 2024 16:49:39 +0000 0 5 <p>Do we have a document that describes the calibration (and other) data that we need to routinely take? After the July experience, it's clear that we need to be more careful about taking the calibrations, and that stability cannot be assumed &#8211; while we <em>think</em> that the problem is the flat field screen, this isn't yet proven (e.g. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kota.hayashi" class="user-hover" rel="kota.hayashi">Kota Hayashi</a>'s results don't yet seem to reproduce the effects we see).</p> <p>So, I think we need a document (pbworks?) which describes the standard calibrations, including how to both take and reduce them. Then these "run" tickets could refer to that general description, and only add extra things that are special. An example would be that in December I think we're going to want to look at how fibres move as we change the flat field screen illumination (e.g. using one ring-lamp at a time).</p> <p>I think it is good idea. In the recent runs, we referred previous tickets, PBworks page, and obslog.. but a dedicated document should exist.. </p> <p>I'm sorry for slow work, but I'm making the procedure here:<br/> <a href="https://sumire.pbworks.com/w/page/155335224/Procedure%20to%20take%20test%20and%20calibration%20data%20during%20engineering%20run" class="external-link" rel="nofollow">https://sumire.pbworks.com/w/page/155335224/Procedure%20to%20take%20test%20and%20calibration%20data%20during%20engineering%20run</a></p> <p>And here are a few comments:</p> <p>I'd suggest to take</p> <ul> <li>Quartz (and arc) at least every night to trace stability</li> <li>(If there is a chance and we can prepare) <ul> <li>Some data to to study dot penumbra</li> <li>Quartz at different Cobra phi/theta position</li> </ul> </li> </ul> <p>Also, we need to make new maskFiles for mod32/mod16 with all SMs if you need ones. Arnaud has updated the mask for fibrProfile, but not for the other items (<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-2123" title="create maskFiles which include all four spectrographs" class="issue-link" data-issue-key="INSTRM-2123"><del>INSTRM-2123</del></a>). </p> <p>For the fiberProfiles, thank you for including the dithers on the dot-roach darks. Could I further request that the dot-roach darks be taken immediately before (or after) the observations they are intended to correct? I understand that this may require an additional fiber move, but I think it's worth it to reduce the possibility of the quartz brightness changing.</p> <p>For the background study, could you also please observe each lamp separately in the mod32 configuration? Data was previously obtained with something like a mod10 configuration, but I think the extra spacing could be helpful.</p> <p>I second Moritani-san's request for quartzes at different cobra positions; I think this will be important to see how good the extraction is when the fibers aren't at the home position. If you have lots of spare time, maybe we could do a complete fiberProfile run (the four sets of mod4 observations) with the exposed fibers at a position that isn't "home", but a position calculated/suspected to have the worst effect on the fiber profile (without going into the black spot penumbra; maybe this is just 180 degrees from the home position?).</p> <p>If "dot-roach" dark means quartz taken after dot-roaching, with all fiber hidden (step 5–7 in the PBworks page), maybe we could take some if we take data one group after another?</p> <p>Previous data were taken during exposure for the PSF modeling... is only mod32 enough?</p> <p>Yes, a "dot-roach dark" is a quartz exposure with all fibers hidden. The current plan is:</p> <ul> <li>dot-roach dark brn, dithered (but I don't see dithering mentioned on the PBWorks page)</li> <li>dot-roach dark bmn, dithered (but I don't see dithering mentioned on the PBWorks page)</li> <li>mod4 traces bmn, dithered</li> <li>mod4 traces brn, dithered<br/> In this case, the brn traces are taken long after the brn dot-roach dark. I would like to minimise the time between taking the "dot-roach dark" and the corresponding exposures with fibers revealed. An example ordering might be:</li> <li>dot-roach dark brn, dithered (but I don't see dithering mentioned on the PBWorks page)</li> <li>mod4 traces brn, dithered</li> <li>dot-roach dark bmn, dithered (but I don't see dithering mentioned on the PBWorks page)</li> <li>mod4 traces bmn, dithered<br/> As I said, this probably means an extra fiber move.</li> </ul> <p>OK, you are requesting to add dithered trace with all fiber hidden behind dot. </p> <p>Just out of curiosity... in July the groups 2,4,4 were taken on after another.. and did you see some instability in allHidden traces? (It was not dithered thought..)</p> <p>If on-telescope time is approved, we should have enough time in this period,, so problably we can separate brn / bmn. We (Arnaud) used this procedure to save time to dot-roaching.</p> <p>I didn't see instability in the quartz fluxes, but I want to be even more sure that it's not lurking.</p> <p>Oh, even more important than the quartz fluxes is the possibility of the fibers moving on the detector due to normal flexure in the instrument over time.</p> <p>We've seen shifts in the July 2023 run (compare dot-roach dark 97774 and quartz 97805 for fiberId=41 on r1). This might be due to the slit not returning to the correct location or optical changes over time, but we can relatively cheaply suppress the latter by taking the dot-roach dark immediately before or after the quartzes they are intended to correct, with no intervening exposures. (I don't think there's a cheap way to suppress the former.)</p> <p>Cobras that fail to reach their destination may be acceptable for science exposures, but for calibs it means we’re going to get sub-optimal measurements for that fiber that will affect it (and potentially neighboring fibers) for the entire run or even longer. I think that means it’s generally worth spending extra time allowing the cobras to converge for calibs.</p> <p>Do we need/want to check hexapod repeatability when doing the dithers? I.e do we want to run [ 0.0, -0.4, -0.2, 0.0, 0.2, 0.4, 0.0 ]?</p> <p>The default sequence is like that. More precisely, (home, -0.4, -0.2, 0.0, 0.2, 0.4, home, and home=0) and if the slit is power off, take 1 frame with power off (so we should slit on before profile) at the beginning and at the end.</p> <p>Regarding to take arc/trace to check illumination pattern with and without flat screen, could you confirm which lamp to be used? PFIlamp to compare the July.. is my understanding correct?</p> <p>Regarding to sparse-sky, Jim told that the dark-sky is most important (and moony sky). so exposure time should be longer to obtain enough count (around half of full fell or less in IR).</p> <p>The run has been finished so I close this.</p> Relates PIPE2D-1303 Development Rank 0|02qpga: Sprint 2DDRP-2023 A