Changes between Version 284 and Version 285 of docs/CommissioningPlan

Timestamp:

08/26/22 11:07:55 (2 years ago)

Author:

kradhakrishnan

Comment:

--

docs/CommissioningPlan

@@ -163 +163 @@
 ||'''#'''||'''Activity Name'''||'''Duration (days)'''||'''Category'''||
 ||P2.0||[wiki:/docs/CommissioningPlan/P2.0 SHARK-NIR Open Cart Activities]||1||C1||
-||P2.0_Pre||[wiki:/docs/CommissioningPlan/P2.0_Pre Cable chain cabling and pre-lift verification]||2||C1||
-||P2.0A||[wiki:/docs/CommissioningPlan/P2.0A Installation of SHARK-NIR and electronics on the LBT platform]||7||C2||
-||P2.0B||[wiki:/docs/CommissioningPlan/P2.0B Installation of SHARK-NIR electronics on LBT platform]||0||C2||
-||P2.1||[wiki:/docs/CommissioningPlan/P2.1 Basic functionality and shutdown procedure test, cryostat cooldown]||0.5||C3||
-||P2.2||[wiki:/docs/CommissioningPlan/P2.2 Instrument operability and functioning]||0.5||C3||
+||P2.1||[wiki:/docs/CommissioningPlan/P2.1 Cable chain cabling and pre-lift verification]||2||C1||
+||P2.2||[wiki:/docs/CommissioningPlan/P2.2 Installation of SHARK-NIR and electronics on the LBT platform]||7||C2||
+||P2.3||[wiki:/docs/CommissioningPlan/P2.1 Basic functionality,  Instrument operability and functioning]||1||C3||
 ||P2.4||[wiki:/docs/CommissioningPlan/P2.4 SHARK-NIR alignment to the telescope]||3||C3||
 || || Total without contingency||14 days  ||
@@ -185 +183 @@
 '''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. If contrast is not an option, a similar (or another) merit function will be used. After completing each of these runs, 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.