35 | | **Phase 3**: The nighttime commissioning commences, starting from sending preset to the telescope to testing individual SHARK-NIR observation cases for performance to the total SHARK-NIR performance. The final form of the SHARK-NIR software, observing blocks, data-reduction pipeline, etc., will be tested for all the observing cases of the instrument. All the activities are at nighttime. Very few daytime activities are anticipated. Science verification of a set of observing cases will be performed immediately after the completion of a set of essential nighttime activities. [Commissioning and Science Verification] |
| 35 | **Phase 3**: Phase 3 commences the nighttime commissioning, starting from sending preset to the telescope to testing individual SHARK-NIR observation modes for performance to the total SHARK-NIR performance. The final form of the SHARK-NIR software, observing blocks, data-reduction pipeline, etc., will be tested for all the observing cases of the instrument. All the activities are at nighttime. However, some daytime activities may be anticipated as well. There will be a common run (Run 1) to test the basic common requirements for each of the observing cases. Run 2-5 blocks represent the nighttime technical commissioning of a set of 17 observing cases. After the completion of each of these runs, SHARK-NIR will be ready for Phase 4 (science verification) of the respective observing cases. [Commissioning] |
| 36 | |
| 37 | **Phase 4**: SHARK-NIR is ready for the final phase of the commissioning - the early science (or science verification) observations. The final performance of the SHARK-NIR will be analyzed using the data from this run. All the activities are at nighttime. By the end of this phase, SHARK-NIR is ready for single-eye shared-risk scientific exploitation. [Early Science or Science Verification] |
| 38 | |
170 | | '''SHARK-NIR Location''': LBT platform. All activities are __nightime__. Some daytime support (within SHARK-NIR) may be required. Also, the SHARK-NIR software, SHINS, is expected to be almost ready to be tested. |
171 | | |
172 | | Phase 3 is further divided into 5 runs. Run 1 consists of essential common activities essential for every observing case. This will be the first to be tested on-sky. Run 2-5 blocks represent the nighttime technical commissioning of a set of 17 observing cases. For each of the observing cases, only one target will be tested. The contrast obtained from the data will be used as the merit function or success criterion. If contrast is not an option, a similar (or another) merit function will be used. After the completion of each of these runs, SHARK-NIR will be ready for Phase 4 (science verification) of the respective observing cases. |
173 | | |
174 | | It is important to note that __Run 2-5 are interchangeable__. It is currently sorted to have the software complexity in the increasing order and also considering the science interest. Note that "Run N" does not mean that it is the Nth visit to the observatory. For example, Run 1 can be completed in 1 or 2 visits to the observatory, depending on the allotted time. Note also that, for individual runs (2-5), the time taken for other basic activities (such as moving from one target to another, setting up the telescope, closing the AO loop, etc.) are not explicitly mentioned in the table. For example, we anticipate, it may take between 10-20 minutes to move and set the telescope and close the AO loop from one target to another (numbers from the LUCI overheads table). This extra duration required will be mostly covered within the 20% contingency and/or the rounding up of the total nights. |
| 174 | '''SHARK-NIR Location''': LBT platform. All activities are __nightime__. Some daytime (within SHARK-NIR) may be required. Also, the SHARK-NIR software, SHINS, is expected to be almost ready to be tested. |
| 175 | |
| 176 | Phase 3 is further divided into 4 runs (Com-Run-#), each corresponding to a trip to LBT. Com-Run-1 consists of essential common activities essential for every observing case. This will be the first to be tested on-sky. Com-Run-2 to Com-Run-4 are__interchangeable__. It is currently sorted to have the software complexity in the increasing order and also considering the science interest. By the end of these 4 runs, all the SHARK-NIR observing cases will be verified on sky. For each of the observing cases, one (or a maximum of two) target(s) will be tested. The contrast obtained from the data will be used as the merit function or success criterion. If contrast is not an option, a similar (or another) merit function will be used. After the completion of each of these runs, SHARK-NIR will be ready for Phase 4 (science verification) of the respective observing cases. |
| 177 | |
| 178 | Note that, for individual runs (2-4), the time taken for other basic activities (such as moving from one target to another, setting up the telescope, closing the AO loop, etc.) are not explicitly mentioned in the table. For example, we anticipate that it may take between 10-20 minutes to move and set the telescope and close the AO loop from one target to another (numbers from the LUCI overheads table). This extra duration required will be mostly covered within the 15% contingency and/or the rounding up of the total nights. |
185 | | ||'''#'''||'''Activity Name / Observing Case'''||'''Duration (hours)'''||'''Seeing Conditions'''||'''Category'''||'''Note'''|| |
186 | | || P3.1 ||[wiki:/docs/CommissioningPlan/P3.2 Telescope control – sending preset, telescope mode, offset, and focal plane geometry estimation]||3||medium / bad||C5|| || |
187 | | || P3.3 ||[wiki:/docs/CommissioningPlan/P3.3 SOUL-AO verification]||6||good / medium||C5 + C7|| || |
188 | | || P3.4 ||[wiki:/docs/CommissioningPlan/P3.4 Pupil alignment] (for checking the pupil positon, and working of the script)||2||bad||C5 + C6|| || |
189 | | || P3.5 ||[wiki:/docs/CommissioningPlan/P3.5 PSF Alignment]||3||good / medium||C5 + C6|| || |
190 | | || P3.6 ||[wiki:/docs/CommissioningPlan/P3.6 Verify the ADC rotation on sky]||4||medium / bad||C5|| || |
191 | | || P3.7 ||[wiki:/docs/CommissioningPlan/P3.7 Checking field-stabilized mode/bearing rotation service]||2||bad||C5|| || |
192 | | || P3.8 ||[wiki:/docs/CommissioningPlan/P3.8 Internal TT loop working and performance] (in different magnitude)||3||good / medium||C5 + C7|| || |
193 | | || P3.9 ||[wiki:/docs/CommissioningPlan/P3.9 NCPA working and performance & checking for pupil shifts]||8||medium (up to 1")||C5 + C7|| || |
194 | | || P3.10 ||[wiki:/docs/CommissioningPlan/P3.10 Check the acquisition procedure]||2||medium||C5|| || |
195 | | || P3.11 ||[wiki:/docs/CommissioningPlan/P3.11 Sky background]||2||bad||C5 + C6|| || |
196 | | || P3.12 ||[wiki:/docs/CommissioningPlan/P3.12 Astrometry plate scale and orientation]||2||good / medium||C5 + C6|| || |
197 | | || P3.13||[wiki:/docs/CommissioningPlan/P3.13 Distortion map]||2||good / medium||C5 + C6|| || |
| 189 | ||'''#'''||'''Activity Name / Observing Case'''||'''Duration (hours)'''||'''Seeing Conditions'''||'''Category'''|| |
| 190 | || P3.1 ||[wiki:/docs/CommissioningPlan/P3.2 Telescope control – sending preset, telescope mode, offset, and focal plane geometry estimation]||3||medium / bad||C5|| |
| 191 | || P3.3 ||[wiki:/docs/CommissioningPlan/P3.3 SOUL-AO verification]||6||good / medium||C5 + C7|| |
| 192 | || P3.4 ||[wiki:/docs/CommissioningPlan/P3.4 Pupil alignment] (for checking the pupil positon, and working of the script)||2||bad||C5 + C6|| |
| 193 | || P3.5 ||[wiki:/docs/CommissioningPlan/P3.5 PSF Alignment]||3||good / medium||C5 + C6|| |
| 194 | || P3.6 ||[wiki:/docs/CommissioningPlan/P3.6 Verify the ADC rotation on sky]||4||medium / bad||C5|| |
| 195 | || P3.7 ||[wiki:/docs/CommissioningPlan/P3.7 Checking field-stabilized mode/bearing rotation service]||2||bad||C5|| |
| 196 | || P3.8 ||[wiki:/docs/CommissioningPlan/P3.8 Internal TT loop working and performance] (in different magnitude)||3||good / medium||C5 + C7|| |
| 197 | || P3.9 ||[wiki:/docs/CommissioningPlan/P3.9 NCPA working and performance & checking for pupil shifts]||8||medium (up to 1")||C5 + C7|| |
| 198 | || P3.10 ||[wiki:/docs/CommissioningPlan/P3.10 Check the acquisition procedure]||2||medium||C5|| |
| 199 | || P3.11 ||[wiki:/docs/CommissioningPlan/P3.11 Sky background]||2||bad||C5 + C6|| |
| 200 | || P3.12 ||[wiki:/docs/CommissioningPlan/P3.12 Astrometry plate scale and orientation]||2||good / medium||C5 + C6|| |
| 201 | || P3.13||[wiki:/docs/CommissioningPlan/P3.13 Distortion map]||2||good / medium||C5 + C6|| |