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-1018 DRP 2-D Pipeline <p>Similar to <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-912" title="Plan for data acquisition November 2021 run" class="issue-link" data-issue-key="PIPE2D-912"><del>PIPE2D-912</del></a>, please provide the plan for Princeton for data acquisition for the May 2022 run, the expected time needed for each activity, if it's a daytime activity etc. and the priority for each activity</p> <p>This is expected to include:</p> <ol> <li>Dot-crossing</li> <li>Dot-roach</li> <li>Isolated fibers for PSF modelling</li> <li>Isolated fibers for odd/even fiber profile modelling</li> <li>Dithered flats.</li> </ol> PIPE2D-1018

Plan for data acquisition May 2022 run

Task Normal Done Done Unassigned hassan EngRun Fri, 8 Apr 2022 15:28:17 +0000 Fri, 23 Sep 2022 04:09:06 +0000 Wed, 1 Jun 2022 18:57:05 +0000 0 6 <p><tt>Regarding point 3, I propose 3 different experiments. I have indicated their priority in the text with ``minimal'', ``medium'' and ``larger''</tt><tt>Total times assume following overheads =&gt; ccd reading overhead = 45 sec, dot-roach fiber movements = 30 min, cobra move = 60 sec. In case that dot-roach time can be reduced, some of the times could be significantly reduced. Also, I assume that for every experiment, we retake dot-roach. As such I hope these estimates are upper limits.</tt></p> <p><tt>Total time needed for ``minimal'' : 145 minutes (2h 25 min)</tt><br/> <tt>Total time needed for ``medium'' (minimal included): 405 minutes (6h 45min)</tt><br/> <tt>Total time needed for ``larger'' (medium included): 16 hours</tt></p> <p><tt>##### study misalignment</tt><br/> <tt># daytime activity, but closed dome</tt></p> <p> <tt># Order of activity</tt><br/> <tt># select fibers that are avaliable in dcb and do not overlap</tt><br/> <tt># These are:</tt><br/> <tt># 2, 63, 192, 255, 339, 401, 464, 525, 587, 650</tt><br/> <tt># 12, 32, 60, 161, 210, 223, 259, 289, 341, 360, 400, 418, 449, 497, 518, 545, 593, 621, 643</tt></p> <p><tt>expose arc neon=140 duplicate=1 (one side of defocus)</tt><br/> <tt>expose arc neon=4 duplicate=2</tt><br/> <tt>expose arc neon=140 duplicate=1 (other side of defocus)</tt></p> <p><tt>all together for one position of cobras = 140+140+4*2+45*4+60 = 440 seconds = 7.5 minutes</tt></p> <p><tt># Priorities</tt><br/> <tt># minimal - at least 10 steps along phi or theta (145 minutes - assume 30 minutes for dot roach)</tt><br/> <tt># medium - at least 10 steps along both phi and theta (210 minutes)</tt><br/> <tt># larger - 10 steps in theta at different phi (e.g., at 3 different fixed values of phi) (360 minutes)</tt></p> <p><tt>##### illumination of all fibers</tt><br/> <tt># daytime activity, but closed dome</tt></p> <p> <tt># Order of activity</tt><br/> <tt># Select every 10th fiber - estimate 30 min</tt></p> <p><tt>expose arc neon=140 duplicate=1 (one side of defocus)</tt><br/> <tt>expose arc neon=4 duplicate=2</tt><br/> <tt>expose arc neon=140 duplicate=1 (other side of defocus)</tt></p> <p><tt>Priority - medium</tt><br/> <tt>3 runs to get good sampling = 195 minutes</tt><br/> <tt>Priority - larger</tt><br/> <tt>10 runs to get everything = 360 minutes</tt></p> <p><tt> </tt><tt>####### Take data that mimics dummy cable B data</tt><br/> <tt># daytime activity, but closed dome</tt></p> <p> <tt># Order of activity</tt><br/> <tt># select fibers 2, 63, 192, 255, 339, 401, 464, 525, 587, 650</tt><br/> <tt># run the command below</tt><br/> <tt># then select fibers 12, 32, 60, 161, 210, 223, 259, 289, 341, 360, 400, 418, 449, 497, 518, 545, 593, 621, 643</tt><br/> <tt># run commands</tt></p> <p><tt>expose arc neon=340 duplicate=3 (one side of defocus)</tt><br/> <tt>expose arc neon=4 duplicate=6</tt><br/> <tt>expose arc neon=340 duplicate=3</tt></p> <p><tt>expose arc argon=850 duplicate=3 (one side of defocus)</tt><br/> <tt>expose arc argon=10 duplicate=6</tt><br/> <tt>expose arc argon=850 duplicate=3 (other side of defocus)</tt></p> <p> <tt>Priority - larger</tt><br/> <tt>8300 second for one set of fibers + 30 min to select fibers = 2.8 hours</tt><br/> <tt>5.6 hours for both ``sets of fibers''</tt></p> <p>Early on, I think we should explore and understand what we can do during the day, under various conditions. The main things we can adjust are the room lights, the Cass cover, the mirror covers, the flat-field screen, and the choice of quartz lamps. The easy configurations are:</p> <ul class="alternate" type="square"> <li>With the dome dark and the cass cover open, we can do nearly all FPS work.</li> <li>With the dome dark, the mirror covers open, the FF screen in place, we can do much SPS work. To use the HSC lamps, we would need staff support, as I understand it.</li> </ul> <p>Beyond those, ee should explore a couple of ways we might be able to run some procedures during the day. One background question is whether there are room light configurations which are acceptable for some staff work which also allow some useful PFS work. Just talking about "room lights on" vs. "dark dome" is, I believe, a bit simple.</p> <p>The biggest questions are:</p> <ul class="alternate" type="square"> <li>can we do anything with the MCS with any room lights on? Specifically, is there is some room light configuration such that we can run convergence? Without this, it is hard to imagine doing anything with the SPS and cobras.</li> <li>can we do <b>anything</b> with the SPS with room lights on and the mirror covers closed? Specifically, whether the dot obscuration is such that we can run the dot-roach procedure. Alternately, can we do anything with the SPS with the room lights off and the mirror covers closed?</li> </ul> <p>To explore this, one afternoon with a helpful observer?</p> <p>Thoughts, @rhl?</p> <p>Being a bit more specific about the dotroach datasets we want :</p> <ol> <li>dotroach<br/> 1. Take at least one dataset where we don't stop any cobras: eg we pass through the dot measuring fluxes with sm1, this will allow us to find the best/robust criteria for stopping the motion.<br/> 2. Then we can play, we are thinking about a command :<br/> iic dotroaches hide=(all|odd|even|none|dcb|filename)<br/> we can try those different configuration and see how good we do</li> </ol> <p>I checked the timing from last time :<br/> <em>sps expose</em> took 30s in total (with exptime=10), reduction(20s), with some overhead around ~55s per step.<br/> we can envision 20-30 steps so, 20-25 minutes per dataset.</p> <p>Hassan and I talked about this ticket and how many hours are expected for day-time work. And the below is what we talked:</p> <ul> <li>I'm planning to split the allocated nights into daytime and nighttime work as follows, following the experiences from the past runs.   <ul> <li>In the past engineering runs, we started the observation at ~5pm and ended at ~6am (i.e. 13 hours for work, and 30min for preparation and cleanup each). </li> <li>The sunset and sunrise is ~6:50pm and ~5:45am, respectively in the middle of May. We can start opening the dome and observation ~+/- 45 min after/before that time.</li> <li>So, roughly, 5pm-7:30pm in the evening and 5am-6am in the morning will be allocated for daytime work (or <em>twilight</em> work) which requires telescope movement and/or darkness, namely, dot-crossing with different EL, and isolated fibers. Note that we should do command flow test too in particular in the evening, so not all the time can be used for DRP.</li> </ul> </li> <li>Since MCS installed on Cs this Friday (29 April), we can check the impact of the room light on the background. (I personally don't think it much since MCS is covered..) If the impact of the room light is small, we can carry out convergence test, dot crossing without moving telescope, before 5pm and after 6am as we discussed with Julien before. (Maybe ~11am to ~4pm on weekdays at maximum, when day crew and others usually works at the summit.) <ul> <li>On the first night, we can try dot-roach with the room light (and bright dome lamp) is on. If it works, we could test dot-roach during daytime, if it is allowed to keep the bright light. For example, you can prepare a given position and standby for data acquisition during twilight..</li> <li>(We should discuss how many hours are needed for convergence test, but this is out of scope of this ticket)</li> <li>The 2nd and 3rd day are weekend, so we should use some twilight/night time for cobra activity if we cannot keep cell cover open.</li> </ul> </li> <li>I have a question to <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> : Could you please tell the background why you need to test dot-crossing at different InR? Is it related coordinate transformation? (Dot rotates with PFI focal plane, so I'm confused..)</li> </ul> <p>Added current working PU data acquisition activities <span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/15166/15166_PU_MayEngRun.md" title="PU_MayEngRun.md attached to PIPE2D-1018">PU_MayEngRun.md^{<img class="rendericon" src="https://pfspipe.ipmu.jp/jira/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span> </p> <p>Consider this closed for an past engineering run.</p> Blocks PIPE2D-1025 Relates PIPE2D-1077 INSTRM-1392 Development Rank 0|02qpjd:041 Sprint 2DDRP-2022 D Story Points 2.0