Changes between Version 8 and Version 9 of docs/CommissioningPlan


Ignore:
Timestamp:
03/10/20 11:58:54 (5 years ago)
Author:
mdepasca
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • docs/CommissioningPlan

    v8 v9  
    3636-----
    3737
    38 {{{Name of the commissioning activity}}}
     38=== Name of the commissioning activity
    3939 - {{{phase}}}: states the phase of the commissioning (1/2/3)
    4040 - {{{status}}}: reports the current status of the test (draft, final, complete)
     
    4242 - {{{recurrence}}}: describes how frequently the test must be executed
    4343 - {{{duration}}}: estimates the time required to complete the test
    44 {{{Description}}}
     44=== Description
    4545•       Contains a general description of the test
    46 {{{Prerequisites}}}
     46=== Prerequisites
    4747•       Lists items that must be in place before the test begins
    48 {{{Procedure}}}
     48=== Procedure
    4949•       Explains in detail how to execute the test
    50 {{{Success Criteria}}}
     50=== Success Criteria
    5151•       Enumerates the outcome associates with successful completion of the test
    52 {{{Notes}}}
     52=== Notes
    5353•       Additional supporting information
    54 {{{LBTO Support}}}
     54=== LBTO Support
    5555•       Mention if (and what) support required from LBTO
    56 {{{Associated SHARK-NIR personnel}}}
     56=== Associated SHARK-NIR personnel
    5757•       Mentions here who are the associated personnel to the test
    58 {{{Date performed and by whom}}}
     58=== Date performed and by whom
    5959•       Mentions who performed the test and when
    6060-----
     61== Additional Information  ==
     62
     63Note:
     64 - as of now, there is no one to one correspondence with the evolving doc (eventually they will be the same)
     65 - you may see that there is some repetition in the activities. this needs to be sorted out eventually.
     66 - the order of the activities may also be changed later.
     67 - the details of each of the activity (when you click on them individually) may not be complete and will be refined in time.
     68
     69To be added:
     70 1. Nighttime performance activities:
     71      - Evaluate the seeing performance and Strehl achieved from the LBTI AO in closed-loop and in various seeing conditions.
     72
     73 2. Look-up table activities:
     74      -  NCPA measurement for different telescope elevations?
     75
     76
     77
     78Reminders:
     79 - The space requirements at the mountain bay (@LBT) should be communicated to LBT at the earliest, along with the availability of crane operator, container moving tools, etc. Depending upon the month of the year, the mountain bay can be seriously booked (especially during July-October months due to summer shutdown).
     80 - The same is true for the cleanroom near the mountain bay. If we need access to the LBTO network in the cleanroom, there are some network ports. But we may need to tell them in advance (Talk to Florian Briegel for more info).
     81 - Note that if there is any ASM repair/activity scheduled in the cleanroom, preference is always for them and we will have to co-live or get after that.
     82 - From the LINC-NIRVANA commissioning experience, it is always better to keep the tools associated with a particular alignment together, to avoid looking for it in all the boxes there. Also, there MUST be a **living inventory** wiki page where everyone should note down what is taken and kept in the box/container.
     83 -  Space required by SHARK-NIR at 3L is already mentioned to JC and CV. Later, we may need to specify the exact area.
     84
    6185== Commissioning Activity ==
    6286In this section, you can see all the commissioning activities listed in chronological order. If you click the individual activity, you can see more details of it.
     
    124148||P3.32||[wiki:/docs/CommissioningPlan/P3.32 PSF Alignment]||Night||-||5||C4||LBTI(AO)||
    125149
     150== Comments ==
    126151
    127 == Additional Information  ==
    128 
    129 Note:
    130  - as of now, there is no one to one correspondence with the evolving doc (eventually they will be the same)
    131  - you may see that there is some repetition in the activities. this needs to be sorted out eventually.
    132  - the order of the activities may also be changed later.
    133  - the details of each of the activity (when you click on them individually) may not be complete and will be refined in time.
    134 
    135 To be added:
    136  1. Nighttime performance activities:
    137       - Evaluate the seeing performance and Strehl achieved from the LBTI AO in closed-loop and in various seeing conditions.
    138 
    139  2. Look-up table activities:
    140       -  NCPA measurement for different telescope elevations?
    141 
    142 
    143 
    144 Reminders:
    145  - The space requirements at the mountain bay (@LBT) should be communicated to LBT at the earliest, along with the availability of crane operator, container moving tools, etc. Depending upon the month of the year, the mountain bay can be seriously booked (especially during July-October months due to summer shutdown).
    146  - The same is true for the cleanroom near the mountain bay. If we need access to the LBTO network in the cleanroom, there are some network ports. But we may need to tell them in advance (Talk to Florian Briegel for more info).
    147  - Note that if there is any ASM repair/activity scheduled in the cleanroom, preference is always for them and we will have to co-live or get after that.
    148  - From the LINC-NIRVANA commissioning experience, it is always better to keep the tools associated with a particular alignment together, to avoid looking for it in all the boxes there. Also, there MUST be a **living inventory** wiki page where everyone should note down what is taken and kept in the box/container.
    149  -  Space required by SHARK-NIR at 3L is already mentioned to JC and CV. Later, we may need to specify the exact area.
     152=== MDP
     153- all operation that should be supported by **control software** automated procedures, should be defined by the reponsible person with software person in copy or in accordance with software department (better) (e.g.: P1.8 and P1.9)
    150154 
    151