1 / 8

Interfaces

Interfaces. Joel Kastner. Interfaces. Widespread consensus exists within the SOFIA Project about the need for cooperation between the DCS, FSI teams, and other important players (e.g. Sterling Software) DCS design process has benefited tremendously from this atmosphere of cooperation

nuala
Download Presentation

Interfaces

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. Interfaces Joel Kastner

  2. Interfaces • Widespread consensus exists within the SOFIA Project about the need for cooperation between the DCS, FSI teams, and other important players (e.g. Sterling Software) • DCS design process has benefited tremendously from this atmosphere of cooperation • For its part, the DCS is proactive in building and maintaining close ties with all parties

  3. Interfaces • Close ties with FSI teams fostered via on-site visits, interface workshops, telecons, & document exchanges • Close contact between DCS and FSI teams facilitates rapid development of DCS instrument commanding and data pipelining • Preliminary observing mode descriptions and commanding scenarios for FORCAST & HAWC received & reviewed; we are iterating with all 4 FSI teams on these designs • Pipeline prototypes are already being developed by DCS w/ considerable assistance from FSI teams

  4. EXAMPLE: FORCAST Observing Mode Parameters (I.e. Astronomical Observing Template [AOT])

  5. EXAMPLE: FORCAST Observing Sequence

  6. EXAMPLE: HAWC Pipeline Requirements • Generate elemental difference images (chop-rate image data) from demodulated sample-rate (ADC rate) data • Process individual elemental difference images to assess noise and remove detector artifacts • Co-add elemental difference images • Integrate coadded difference images for each telescope pointing in a “stare & nod” sequence • Combine dithered image series into a mosaic • Calibrate final, combined image intensities & establish image coordinate system • Merge/correlate image data with contemporaneous ancillary (HK, telescope, observatory) data • Produce archive-quality products at each major processing step

  7. EXAMPLE: Prototype HAWC Pipeline • Developed in vanilla IDL • Uses data output by prototype HAWC simulator (author: B. Loewenstein) Demodulate sample-rate data Coadd chop-rate images

  8. EXAMPLE: HAWC Data Products * = product archived by DCS (TBR) • ADC sample-rate pixel (telemetry) stream • demodulated, “raw” elemental difference images • cleaned, deglitched elemental difference images • coadded elemental difference images* • merged, “final” dithered image w/ coordinate system attached* • image calibration files (and other ancillary data files)* • bad pixel & glitch mask • image noise characterization • flat field • telescope pointing history • global HK data (HAWC, telescope, observatory)

More Related