1 / 14

Data reduction library I. requirements Eric Bakker

Data reduction library I. requirements Eric Bakker. I. Requirements II. Design (Jeroen) III. Implementation (Jeroen) IV Operations. Categories. Scientific performance Technical performance User interfaces Data flow interfaces Quality control Simulations Trend analysis Calibration

adlai
Download Presentation

Data reduction library I. requirements Eric Bakker

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. Data reduction libraryI. requirementsEric Bakker I. RequirementsII. Design (Jeroen)III. Implementation (Jeroen)IV Operations PRIMA AOS CDR

  2. PRIMA AOS CDR

  3. Categories • Scientific performance • Technical performance • User interfaces • Data flow interfaces • Quality control • Simulations • Trend analysis • Calibration • Software design • Software implementation PRIMA AOS CDR

  4. Category 1/10Scientific performance • 10 micro-arcsecond calibrated data • Verification of performance • sets of visual binaries • simulated data sets PRIMA AOS CDR

  5. Category 2/10Technical performance • Processing time • Pipeline solution < 5 minutes (for 1 OB) • Nightly solution < 8 hours (full night of data) • Global solution < 5 days (for full data-set) • Installation • self-contained, auto install • IDAF versus pipeline • Documentation • Central WW-site on-line access • incode extensive description by developers • Error handling PRIMA AOS CDR

  6. Category 3/10User interfaces • Flexibility • Settting constraints • insert spectrum • Doppler orbit etc. if available • Anomaly handling • software limits on variables PRIMA AOS CDR

  7. Category 4/10Data flow interfaces • Data flow in to the DRS/pipeline • ESO PRIMA OS product • Data flow within the DRS/pipeline • calibration engine, format TBD • Data flow out of the DRS/pipeline • IAU standard astrometric FITS PRIMA AOS CDR

  8. Category 5/10Quality control • Quality control (both IDAF as pipeline) on the subsystem performance should be quantified • STS, MET, FSU, DDL • Quality control on the data reduction chain • Long-term stability, repeatability • Quality control on the observing efficiency • TBD PRIMA AOS CDR

  9. Category 6/10Simulations • Sets of simulated data should be produced • 3 sets • These sets can be feed back to the DRS • Each module should have a simulation mode PRIMA AOS CDR

  10. Category 7/10Trend analysis • Determination of parallax • Determination of proper motion • Extensive (manual) trending of parameter A versus B, and other non-linear combinations. PRIMA AOS CDR

  11. Category 8/10Calibration analysis • IDAF uniformly calibrates data over the period of the program • Pipeline uses the calibration parameters of the IDAF (the calibration engine concept) • Correct for dispersion effects • Correct for polarization effects • Correct for elevation effects • Correct for the color of the star PRIMA AOS CDR

  12. Category 9/10Software design • Allow evolution of DRS PRIMA AOS CDR

  13. Category 9/10Software implementation • Version control • Weekly builds • Comply with ESO standards • If no ESO standards available, define standards to be proposed to ESO PRIMA AOS CDR

  14. Closing words • Requirements do not provide new insights • Requirements aim to define the deliverable • Sabine will continue this work • Next steps • Try to quantify the requirements PRIMA AOS CDR

More Related