Big BOSS Instrument Control System Klaus Honscheid OSU

Big. BOSS Instrument Control System Klaus Honscheid (OSU) DOE Review of Big. BOSS, Dec. 6 -7, 2011

Topics • • • What is the Instrument Control System What are the requirements Who is working on this Design ideas What is the scope of the R&D Summary Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 2

Instrument Control Readout System • • Transfer image data from front end electronics to storage device Orchestrate exposure sequence — Focal plane system incl. fiber positioner — Hexapod, ADC • Interface with Mayall telescope control system Requirements: Complete readout and pointing changes < 60 s Guider signals to TCS at ~ 1 Hz Archive images (Fits), Interface to Data Management Monitor System • Focal plane thermal systems • Telescope, dome, environment • Spectrograph and CCD environment • Cooling system Requirements: Monitor and archive instrument operation and environment Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 3

Big. BOSS ICS Team • The Big. BOSS Instrument Control System is an Ohio State responsibility • Current team members: Klaus Honscheid L 2 Manager 20+ years experience with DAQ systems (DES, BOSS, BTe. V, Ba. Bar, CLEO) Ann Elliott System Analyst DES readout and control system Shane Smith Electrical Engineer BOSS DAQ and electronics (ATLAS front end electronics) Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 4

Exposure Sequence < 60 seconds Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 5

Readout and Dataflow • 10 Spectrographs each with 3 Cameras — 4 k x 4 k CCD, four readout channels — Nominal pixel clock: 100 Kpixels/s Readout time ~ 42 seconds — 16 -bit ADCs — 34 Mbytes per camera Image size ~ 1 Gbyte • Baseline Design — 30 identical slices — use standards and commercial items as soon as possible in the data flow Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 6

Big. BOSS Data Acquisition Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 7

Instrument Monitoring and Control • • Monitor operations of all Big. BOSS components Detect failures and errors Alert observers, operators, experts Log telemetry information in (instrument) database • Critical components (e. g. cooling) require 24/7 monitoring — ICS support required even if DAQ system is off — Hardware protection outside scope of ICS • Will try to standardize control interfaces — Network enabled controller — Low level code provided by component — High level code provided by ICS Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 8

Interface to Mayall TCS • Similar to DECam – Blanco TCS Interface • Communication link between processes in the Mayall TCS and the Big. BOSS DAQ system • Exchange coordinates, guider corrections, position, dome + environment information Mayall Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 9

Online Software Architecture • Infrastructure Software Layer — Message passing — Database interface — other common services • System Software Layer — Configuration system — Alarms & error reporting Follow DES approach (for example) • Application Software Layer — Observation control — Instrument monitoring — Quality assurance • User Interfaces — Web based — Model-view-controller pattern Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 10

R&D Projects • Define sub-system interfaces and write ICS requirements document(s) • Evaluate infrastructure software solutions • Prototype interface to Big. BOSS components • Conceptual design of DAQ-CCD frontend interface • Conceptual DAQ design • Exposure Sequencer • [Subsystem software support] Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 11

Extend BOSS DAQ Concepts • We built the BOSS DAQ system • Conceptually this matches our needs very well but can the design be extended to meet Big. BOSS requirements? Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 12

Evaluate DES Online Software • • • Application software on top of infrastructure layer Multi-process communication (Client-Server Pattern) Shared Variables (Publish-Subscribe Pattern) • Python based • • No commercial components Software Management — Code repository (svn) — Release system (eups) — Configuration (custom design) Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 13

Evaluate LSST Infrastructure • • Ongoing development Collaborate with LSST developers D. Mills (NOAO), G. Schumacher (CTIO) Infrastructure and Application Layer System Architecture Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 14

Summary • The Big. BOSS ICS is responsible for — Data readout and transfer — Instrument control — Instrument and environmental monitoring • Preliminary design of the readout system uses 30 identical slices – one module per camera • Tiered approach to online software similar to models successfully adopted by DES and LSST • Focused R&D program • Experienced development team in place at Ohio State • We are ready to start Dec. 7, 2011 Klaus Honscheid Talk B 5. 1 Instrument Control System 15