1 / 9

CTIO Blanco WF Imager Data Acquisition

CTIO Blanco WF Imager Data Acquisition. Jon Thaler Fermilab, Dec. 6, 2003. MONSOON Pixel Server. Focus on this connection for a moment. MSL (MONSOON Supervisory Level. Nick Buchholz (12/1/03). Crude specs. Assume: • 60 CCD s@ 2k 4.6k with 2 amps (E2V)

ksena
Download Presentation

CTIO Blanco WF Imager Data Acquisition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CTIO BlancoWF ImagerData Acquisition Jon Thaler Fermilab, Dec. 6, 2003

  2. MONSOON Pixel Server Focus onthis connection for a moment MSL (MONSOON Supervisory Level Nick Buchholz (12/1/03)

  3. Crude specs Assume: •60 CCDs@ 2k4.6k with 2 amps (E2V) •1 MHz pixel digitization and read rate Read time is 4.6 s per CCD. 2 bytes per pixel 9 109 bits per image • Exposure time > 600 sec / 10 (0.5 TB/night)(Mohr/Annis) > 120 parallel DAQ channels  dead time below 8%. > Time average data rate (DHEPAN) ~ 1.2 Mbps/chan  ~150 Mbps total. There is a mismatch between CCD readout and DHE  PAN fiber rate requirements. Monsoon architecture issue?

  4. 8 channelseach NEWFIRMImplementation( Mark Hunten’s presentation at12/1/03 Monsoon Status review) Naïve Scaling:Cost ~ $200k Power ~ 300 W

  5. Space on the Telescope NEWFIRM uses a standard 19” crate We will require two, if this is the route we take. We need to worry about space and power.

  6. Software • Pixel Acquisition Node (PAN) SW resides in a PC. • Detector Head Electronics (DHE) SW can either be implemented in a processor or as firmware (FPGA). • Communications is via Systran fiber optics interfaces. • PAN SW (at least for NEWFIRM) has been implemented by the Monsoon group. • A DHE SW emulator for the PC has been written byNick Buchholz (partial implementation?). • DHE SW is detector dependent, and wil be a major project.

  7. Pixel Acquisition Node (PAN) Layer • No knowledge of other PAN-DHE pairs. • Provides PPX interface to MSL or users. • Provides run-time configuration of PAN/DHE. • Provides first level data archiving. • Provides multiple image processing ‘modes’. • Fowler Sampling, coadds, MSR techniques, OT imaging. • Provides parameter verification/control/help. • Deals with IR/OUV/etc. differences. • Handles single exposure sequencing. • Handles raw data pre-processing. • Provides interface to DHE hardware. • Provides DHE sequencer configuration/download. • Provides PAN error monitoring/reporting/recovery. • Provides support for ‘speed ROI’. • Provides support for ‘compression ROI’s’.

  8. Detector Head Electronics (DHE) Layer • Handles array hardware control.Voltage levels, sequencing, monitoring. • Handles integration timing. • Handles detector readout sequencing. • Handles digital averaging. • Handles shutter control. • Can handle array temperature control. • Board Self Identification and Version tracking. Some of this is DAQ and some is “front end.”

  9. Near Term Plans • Buy a pair of Systran PCI cards to study DHE/PAN communications. Fermilab should probably to the same,so we can coordinate. • We must define boundaries and allocate responsibilities. • Emulator verification. • DHE controller specs? Awaits a sensor decision? • Are Systran cards overkill? (e.g., they can do broadcast).How can cost be kept down?

More Related