Changes between Version 20 and Version 21 of docs/CommissioningPlan


Ignore:
Timestamp:
09/28/20 16:04:56 (4 years ago)
Author:
kradhakrishnan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • docs/CommissioningPlan

    v20 v21  
    157157- 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)
    158158 
    159 ===Kalyan
    160 
    161 8.2     Communications and SW related interfaces
    162 SHARK-NIR control software (SHINS) will be interfaced with the following LBT software (further details are reported in RD8):
    163 •       TCS: the availability, both nighttime and daytime, of all IIF methods reported  in RD11 is assumed.
    164 SHINS will need from IIF additional functionalities related to AO:
    165 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.
    166 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.
    167 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.
    168 •       AOS through the engineering programmatic interface:
    169 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.
    170 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.
    171 •       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.
    172 •       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.
    173 •       Archive: observation frames in  the form of FITS files will be sent to the LBTO archive for ingestion using Unix utility rsync (see RD11).
    174 •       Queue/OT: the interface with SHINS will be an XML file, as specified in RD11.
    175 
    176 •       Network (see Figure 5 as reference):
    177 o       Network subnet dedicated to the instrument, to be associated to the instrument workstation and instrument electronics, as well as scientific camera workstation.
    178 o       On commissioning, support to connect the instrument to LBT network will be needed.
    179 o       On commissioning, support will be needed to connect scientific camera control electronics to scientific camera workstation in control room on level 2 (AD5).
    180 •       Workstation installation and instrument operation:
    181 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).
    182 o       On commissioning, access to control room will be needed to operate the instrument.
    183 o       On commissioning, possibility to connect laptop to observatory network to troubleshoot the instrument.
    184 o       On commissioning, software support will be needed during instrument operation involving telescope and IIF.
    185 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.
    186 o       On commissioning, support will be needed with operation involving file archiving in the observatory archive.
     159=== Software Related Stuff / Activities / Reminders
     160
     161 - Capability to set Waffle mode to ASM in closed-loop (SOUL-AO)
     162 - Capability to set an offset shape to ASM in closed-loop for NCPA characterization/removal
     163
     164 - Connection b/w scientific camera control electronics to scientific camera workstation in the control room on level 2.
     165 - access to the server room. support will be needed to install the instrument workstation (1U Dell server) and to install the scientific camera workstation in the control room on level 2
     166
    187167
    188168 
    189 Figure 5: Instrument control network
    190 8.3     Available volume and HW interfaces
    191 The instrument will connect to the existing outer ring of the Gregorian bearing at the central bent focal station, SX side.
    192 The identification of the maximum available volume will pass through some iterative steps:
    193 •       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).
    194 •       The design agreed with INAF-Padova shall be then iterated with LBTO to confirm the space availability.
    195 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.
    196 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.
    197 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”.
    198 
    1991698.4     Installation interfaces
    200170All 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: