Changes between Version 289 and Version 290 of docs/CommissioningPlan

Timestamp:

09/21/22 10:13:06 (2 years ago)

Author:

kradhakrishnan

Comment:

--

docs/CommissioningPlan

@@ -1 @@
-= SHARK-NIR Commissioning Plan (SHARK-NIR-INAFP-COM-001 Issue 0.8)=
+= SHARK-NIR Commissioning Plan (SHARK-NIR-INAFP-COM-001 Issue 0.9)=
 [[TOC(inline)]]
 
@@ -12 +12 @@
 || 0.7 || 18-May-2022 || First page Phase 1 table ||Updating the duration for the re-alignment|| KRA ||
 || 0.8 || 13-Aug-2022 || First page Phase 1 & 2 tables, P1.1 to P1.12 ||Updating after Pre-Com-Run-1|| KRA ||
+|| 0.9 || 21-Sept-2022 || First page Phase 2 table, P2.5 to P2.10 ||Updating before Pre-Com-Run-2|| KRA ||
 
 
@@ -124 +125 @@
 In this section, all the commissioning activities are listed in chronological order. If you click on the individual activity, you can find more details. __8 hours is considered as the duration of a day__. Of course, depending on the month of the year, make sure to estimate the correct number of days/nights required at the LBT. Each table below corresponds to a trip to LBT. 
 
-From commissioning experience at the LBT, for the daytime activities at the telescope platform, the telescope may be handed over around 09:00 am local time. And, the SHARK-NIR team needs to hand over the telescope to LBT ~2 hours before the sunset (unless we have the first half of the night or full night and to be negotiated with the telescope operator). As a general rule, the SHARK-NIR team will also be working on the weekends when at the summit. Of course, if LBTO support is required, this will be communicated with the LBTO mountain manager well in advance. Note that the duration of the individual activities mentioned in this document will not match that of AD4 for the same activities. 
+From the commissioning experience at the LBT, for the daytime activities at the telescope platform, the telescope may be handed over around 09:00 am local time. And, the SHARK-NIR team needs to hand over the telescope to LBT ~2 hours before the sunset (unless we have the first half of the night or full night and to be negotiated with the telescope operator). As a general rule, the SHARK-NIR team will also be working on the weekends when at the summit. Of course, if LBTO support is required, this will be communicated with the LBTO mountain manager well in advance. Note that the duration of the individual activities mentioned in this document will not match that of AD4 for the same activities. 
 
 === Phase 1 (Pre-commissioning) ===
@@ -172 +173 @@
 **__Pre-Com-Run-3__**
 ||'''#'''||'''Activity Name'''||'''Duration (days)'''||'''Category'''||
-||P2.5||[wiki:/docs/CommissioningPlan/P2.5 TCS communication test]||1||C3||
-||P2.6||[wiki:/docs/CommissioningPlan/P2.6 Cryostat Cooldown and Science detector calibrations]||1||C3 + C4||
-||P2.7||[wiki:/docs/CommissioningPlan/P2.7 SHARK-NIR system level characterization at different telescope elevations]||6||C3 + C4||
-||P2.8||[wiki:/docs/CommissioningPlan/P2.8 Star center Fourier mode images]||0.5||C3||
-||P2.9||[wiki:/docs/CommissioningPlan/P2.9 Verification of the mask centering algorithm and final contrast with SOUL-AO and turbulence at ASM]||3||C3 + C4||
+||P2.5||[wiki:/docs/CommissioningPlan/P2.5 Instrument functional checks including TCS communication test]||1||C3||
+||P2.6||[wiki:/docs/CommissioningPlan/P2.6 Tip-Tilt internal fast loop test with ASM turbulence]||0.5||C3||
+||P2.7||[wiki:/docs/CommissioningPlan/P2.7 SHARK-NIR system level NCPA characterization at different telescope elevations]||4||C3 + C4||
+||P2.8||[wiki:/docs/CommissioningPlan/P2.8 Verification of the mask centering algorithm and final contrast with SOUL-AO and turbulence at ASM]||3||C3||
+||P2.9||[wiki:/docs/CommissioningPlan/P2.9 Star center Fourier mode images]||1||C3||
+||P2.10||[wiki:/docs/CommissioningPlan/P2.10 Test of all the remaining templates for sky observations]||2 (TBC)||C3||
 || || Total without contingency||11.5 days  ||
 || || Total with 10% contingency||**12.5 days** ||
@@ -194 +196 @@
 '''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. 
 
-Phase 3 is further divided into 4 runs (Com-Run-#), each corresponding to a trip to LBT. Com-Run-1 consists of 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 observing case, 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. A similar (or another) merit function will be used if contrast is not an option. After completing each run, SHARK-NIR will be ready for Phase 4 (science verification) of the respective observing cases.
+Phase 3 is further divided into 4 runs (Com-Run-#), each corresponding to a trip to LBT. Com-Run-1 consists of 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 observing case, 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. A similar (or another) merit function will be used if contrast is not an option. After completing each run, SHARK-NIR will be ready for Phase 4 (science verification) of the respective observing cases.
 
 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.