![(please configure the [header_logo] section in trac.ini)](/trac/sharknir/chrome/site/SHARK_logo.png){kind=logo}
| Version 11 (modified by kradhakrishnan, 4 years ago) (diff) |
|---|
SHARK-NIR Commissioning Plan
Table of Contents
This document lays out the procedures and performance requirements for commissioning the SHARK-NIR instrument. Specifically, it lists the on-telescope activities needed to bring SHARK-NIR online for scientific exploitation starting from unpacking the boxes at LBT with the exception of the instrument installation at the LBT Bent Gregogian Central focal station.
The commissioning is broadly divided into three phases:
Phase 1: We start from inspecting the boxes at LBT mountain bay, unpacking and installing the instrument at the mountain lab for alignment verification and functionality checks. All of these are daytime activities.
Phase 2: The activities after the installation of SHARK-NIR at the SX central bent Gregorian focus of LBT to the acquirement of the first nighttime telescope collimation model of the instrument form the Phase 2. Most of the activities are daytime. The only nighttime activity is to check the pointing, acquisition sequence and getting the first nighttime telescope collimation model for SHARK-NIR.
Phase 3: Phase 3 of the commissioning starts from sending preset to the telescope to testing individual SHARK-NIR observation modes for performance to the total SHARK-NIR performance. All the activities are nighttime. By the end of this phase, SHARK-NIR is ready for Science Verification.
Note that the corresponding evolving doc in SHARK-NIR Dropbox folder is SHARK-NIR-INAFP-COM-001_CommissioningPlan.docx. There is also an excel file listing the activities titled SHARK-NIR-INAFP-COM-002_CommissioningActivityList.xlsx.
Applicable Documents
| No. | Title | Number & Issue |
| AD1 | SHARK-NIR Schedule | SHARK-NIR-INAFP-SCH-001_Issue 1.2.pdf |
| AD2 | SHARK-NIR SW ICD | SHARK-NIR-INAFP-SW-ICD-FDR Issue 0.4 |
| AD3 | SHARK-NIR Installation Plan | SHARK-NIR-INAFP-IP-001 Issue 0.1 |
| AD4 | SHARK-NIR Calibrations | SHARK-NIR-INAFP-MAN-004 |
Category
The table below lists the categories of commissioning activities.
| Category Name | Category Number |
| Installation, integration, verification | C1 |
| Daytime testing (functionality and operability) | C2 |
| Daytime calibration | C3 |
| Nighttime testing (functionality and operability) | C4 |
| Nighttime calibration | C5 |
| Nighttime testing for performance | C6 |
Naming structure of the commissioning activity
Each commissioning test/activity has a unified structure as follows:
Name of the commissioning activity
- phase: states the phase of the commissioning (1/2/3)
- status: reports the current status of the test (draft, final, complete)
- category: one of the categories mentioned above
- recurrence: describes how frequently the test must be executed
- duration: estimates the time required to complete the test
Description
- Contains a general description of the test
Prerequisites
- Lists items that must be in place before the test begins
Procedure
- Explains in detail how to execute the test
Success Criteria
- Enumerates the outcome associates with successful completion of the test
Notes
- Additional supporting information
LBTO Support
- Mention if (and what) support required from LBTO
Associated SHARK-NIR personnel
- Mentions here who are the associated personnel to the test
Date performed and by whom
- Mentions who performed the test and when
Additional Information
Note:
- as of now, there is no one to one correspondence with the evolving doc (eventually they will be the same)
- you may see that there is some repetition in the activities. this needs to be sorted out eventually.
- the order of the activities may also be changed later.
- the details of each of the activity (when you click on them individually) may not be complete and will be refined in time.
To be added:
- Nighttime performance activities:
- Evaluate the seeing performance and Strehl achieved from the LBTI AO in closed-loop and various seeing conditions.
- Look-up table activities:
- NCPA measurement for different telescope elevations?
Reminders:
- 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).
- 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).
- 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.
- 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.
- Space required by SHARK-NIR at 3L is already mentioned to JC and CV. Later, we may need to specify the exact area.
Commissioning Activity
In 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.
Phase 1
SHARK-NIR Location : LBT mountain bay and clean room
| Number | Activity Name | Day / Night | Duration (mins) | Maximum Duration (mins) | Category | LBTO Support |
| P1.1 | Inspection of the boxes | Day | 40 | 40 | C1 | - |
| P1.2 | Opening boxes and their visual inspection | Day | 60 | 60 | C1 | crane operator to lift and move containers/boxes, 1-2 crew to support unpacking and moving |
| P1.3 | Install the instrument in the cleanroom with its electronics cabinet | Day | 240 | 240 | C1 | crane operator to lift and move containers/boxes, 1-2 crew to support installation on the mechanical structure |
| P1.4 | Cable in the instrument, power on, and connect to LBT network | Day | 120 | 120 | C1 | support to connect to LBT network? Any electronics support? |
| P1.5 | Start all the services and initialize all the motors | Day | 20 | 20 | C1 | - |
| P1.6 | Cool down the cryostat | Day | 480 | 480 | C1 | Liquid N2 fill |
| P1.7 | Verification of the operability of the motors and light sources | Day | 60 | 60 | C1 | - |
| P1.8 | Verification of the internal alignment of the instrument | Day | 120 | 120 | C1 | - |
| P1.9 | Science detector calibrations | Day | 60 | 60 | C1 | - |
Phase 2
SHARK-NIR Location : LBT platform
| Number | Activity Name | Day / Night | Duration (mins) | Maximum Duration (mins) | Category | LBTO Support |
| P2.1 | Activating the instrument and testing instrument states & transitions | Day | 60 | 60 | C2 | Verify the working of emergency button |
| P2.2 | Instrument operability and performance | Day | 180 | 180 | C2 | - |
| P2.3 | TCS communication test | Day | 60 | 60 | C2 | Authorise SHARK-NIR, connecting to ASM+LBTI AO system, able to send preset, receiving LBT telemetry and details for the fitswriter |
| P2.4 | Align SHARK-NIR to the telescope | Day | 120 | 120 | C2 | Mounting RR on the SX side. Support from LBTI? |
| P2.5 | Synergy with LBTI AO system test | Day | 120 | 120 | C2 | Mounting RR on the SX side. Support from LBTI for AO running |
| P2.6 | Measurement of NCPA | Day | 180 | 180 | C3 | Mounting RR on the SX side, Support from LBTI for AO running |
| P2.7 | Looking for filter defects/effects/features | Day | 60 | 60 | C2 | Support from LBTI for AO running |
| P2.8 | Flexure tests | Day | 180 | 180 | C2 | Support from LBTI for AO running |
| P2.9 | Nighttime acquisition and setting telescope collimation for night | Night | 180 | 180 | C4 | Support from LBTI for AO running |
Phase 3
SHARK-NIR Location : LBT platform
Comments
MDP
- all operation that should be supported by control software automated procedures should be defined by the responsible person with software person in copy or in accordance with software department (better) (e.g.: P1.8 and P1.9)
===Kalyan
8.2 Communications and SW related interfaces SHARK-NIR control software (SHINS) will be interfaced with the following LBT software (further details are reported in RD8):
- TCS: the availability, both nighttime and daytime, of all IIF methods reported in RD11 is assumed.
SHINS will need from IIF additional functionalities related to AO: o Set a waffle mode to the ASM, in closed-loop. This functionality will be used night-time before each observation, in order to correctly center the target on the coronagraphic mask (see SHARKNIR-SCI-08 in RD11). The maximum magnitude for the waffle is TBD. o Set an offset shape to the ASM, in closed-loop, specified via a TBD number of Zernike coefficient, for NCPA characterization (see SHARKNIR-TEC-01 RD11). The mirror signals have to be subtracted to rightly correct for atmospheric distortion. This functionality will be used both night-time and day-time, depending on stability of NCPA (see SHARKNIR-TEC-01 in RD11), which will be assessed during commissioning. The rate of ASM offsets sent from SHINS is TBD, as well as the list of errors to be propagated from the AOS to SHINS through the IIF. o Use the telescope “repoint mode” when the telescope is acquiring the AO reference star, so to position the star where the wave front sensor is expecting it to be.
- AOS through the engineering programmatic interface:
o in order to offset the LBTI-WFS position (using X-Y-Z stages), so to align it to SHARK-NIR optical path. This will be needed during commissioning. TBD if the same interface will be used in day-time to adjust for changes. o To set an offset shape to the ASM in closed-loop, in case the requested method from the IIF can apply offsets with a maximum rate lower than the TBD required.
- LBTO telemetry: SHINS telemetry will be written on HDF5 files as requested in RD12. SHINS will access telescope and AO telemetry using the TCS data dictionary via the IIF method GetParameter?.
- Alarm system: using the INDI protocol, SHINS will publish its alarm signals and the statuses of all SHARK-NIR hardware devices and SHINS components, by providing the information required in RD13.
- Archive: observation frames in the form of FITS files will be sent to the LBTO archive for ingestion using Unix utility rsync (see RD11).
- Queue/OT: the interface with SHINS will be an XML file, as specified in RD11.
- Network (see Figure 5 as reference):
o Network subnet dedicated to the instrument, to be associated to the instrument workstation and instrument electronics, as well as scientific camera workstation. o On commissioning, support to connect the instrument to LBT network will be needed. o On commissioning, support will be needed to connect scientific camera control electronics to scientific camera workstation in control room on level 2 (AD5).
- Workstation installation and instrument operation:
o On commissioning, access to server room and support will be needed to install instrument workstation (1U Dell server) and to install scientific camera workstation in control room on level 2 (AD5). o On commissioning, access to control room will be needed to operate the instrument. o On commissioning, possibility to connect laptop to observatory network to troubleshoot the instrument. o On commissioning, software support will be needed during instrument operation involving telescope and IIF. o On commissioning, software support will be needed to build observation blocks with observatory observation preparation tool, which will be then run on the instrument. o On commissioning, support will be needed with operation involving file archiving in the observatory archive.
Figure 5: Instrument control network 8.3 Available volume and HW interfaces The instrument will connect to the existing outer ring of the Gregorian bearing at the central bent focal station, SX side. The identification of the maximum available volume will pass through some iterative steps:
- The SHARK-NIR mechanical design will be finalized by industry under INAF-Padova responsibility. INAF-Padova will provide the optical design (including full rays path).
- The design agreed with INAF-Padova shall be then iterated with LBTO to confirm the space availability.
INAF-Padova will provide the proper mechanical drawings with the purpose to clarify both the available volume to design the SHARK-NIR instrument and the possible connection points. INAF-Padova will also ensure proper communication and exchange of information between LBTO, LBTI and the company in charge of the study for a proper interface definition. We consider as a reference for mechanical interfaces between SHARK-NIR and LBTI the CAD model “SHARK Installation Final.stp” (RD4), which is a merging of the CAD model LBTI_1_20_17 received by Manny Montoya, the CAD model of the gallery “513s Full Gallery Assy 2018 vs - Copy” received by Jim Wiese and the results of the laser tracking survey on SHARK-NIR area conducted by Mike Gardiner “SHARK IR volume measurement2”.
8.4 Installation interfaces All the checks to verify the feasibility of the installation procedure of SHARK-NIR have been performed on the CAD model “SHARK Installation Final.stp”. For installation purposes, the requirements to LBTO are:
- Remove the door of the Nystrom LBTI top hatch (SX side).
- Installation of the rotator work platform at the central bent focal station, SX side.
- Use of the dome crane, to lower the subsystems of SHARK-NIR (as described in AD6) through the hatch in the UIAP LBTI platform and from the M1 side.
- Operator to move the crane.
- General assistance during the mounting phases.
8.5 Electrical interfaces SHARK-NIR electronics design is reported in AD5.
- Summary of required space in the rack (total space: 13U):
o The motor control unit dimensions are 483mm (width) x 133,35mm (height) x 525mm (depth) (also indicated as 19‘‘ × 3U × 525 mm) o The dimensions of the Lake Shore 336 temperature controller are 435 mm W × 89 mm H (2U) × 368 mm D (17 in × 3.5 in × 14.5 in) o Custom realized box: (2U in height) may contain the 2 light sources and their power supply, a motorized linear stage (M-403.2DG from Physik Instrumente), a small optical system consisting of 2 lenses and 1 filter to select the light to inject into the integrating sphere of SHARK-NIR (broadband or multi-narrow bands), the TT camera power supply and the power switches board (relais board) o DM electronics is contained in a 19” × 4U o WFC BCU housing: 19” × 2U (TBC)
- Power requirement (total Watt dissipation: 700W):
o The motor control unit maximum power consumptions is ~350W. o The Camera temperature controller maximum power consumption is of the order of ~100W. Its power requirement is 100, 120, 220, 240 VAC, ±10%, 50 or 60 Hz, 250 VA. o The C-RED2 camera needs a 12V power supply and a commercial “relais” board controllable through Ethernet, is required, to power the power supply, which has a power dissipation of the order of 10W. Custom box: power to be dissipated of the order of 100W o DM electronics power consumption is 150W. o WFC BCU: 24Vdc (48Vdc is also possible upon request) and the estimated power consumption is ~15W The agreed cabinet to allocate the above described electronics is rack 2, referring to Figure 6. The space reserved to SHARK-NIR electronics is the lowest area of the cabinet.
Figure 6: the agreed cabinet for SHARK-NIR electronic is #2. 8.6 Thermal interfaces
- Cooling:
o Daily refill of the cryostat: one LN2 refill per day is required (~10 liters). The camera LN2 hold time is of the order of 28 hours (computed in very conservative conditions, see AD7), giving a reasonable margin on the refilling time. o Liquid cooling of the technical camera C-RED 2 from First Light (through LBTO glycol system, described in RD9): Max temperature: 35°C Min Temperature: dew point Pressure: 10 bar max Cooling capacity: 100W minimum Flow rate: > 0.5 L/min Max 50% ethylen glycol aqueous solution ; 50% distilled water or deionized water
8.7 Other interfaces
- Air Flow:
o A clean air flow with a maximum required flux of 0.5 m3/min to keep SHARK-NIR optical bench on a slight over-pressure with respect to the outer environment. 8.8 Logistics 8.8.1 Connections An Ethernet cable should reach the computer rooms located at level 2. 8.8.2 Storage Space (TBD) for storage should be made available at 3L.
