1 / 4

Enhancing HST Data Retrieval with On-The-Fly Reprocessing (OTFR) for WFC3

The On-The-Fly Reprocessing (OTFR) system optimizes Hubble Space Telescope (HST) data retrieval by reprocessing science data directly from Level 1A pod files at the time of request. This ensures users receive the best possible data products with all recent calibration updates, bug fixes, and software enhancements applied. OTFR utilizes the same processing code as pre-archive science data, minimizing software development costs and ensuring consistency across pipelines. With negligible retrieval time increases and a unified operator interface, OTFR simplifies the data access process for WFC3 users.

irina
Télécharger la présentation

Enhancing HST Data Retrieval with On-The-Fly Reprocessing (OTFR) for WFC3

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. On-The-Fly Reprocessing (OTFR) for WFC3Generating the best-possible data products at archive retrieval time.

  2. OTFR (On-The-Fly Reprocessing) • Science data requested from the archive are reprocessed from the pod file (level 1A data) • Provides HST data user with optimal product at time of retrieval • All calibration updates, bug fixes, and new software features and algorithms are applied to retrieved data at retrieval time • OTFR pipeline uses the exact same code as the pre-archive science data processing • No added software development and maintenance costs • No science instrument-specific code developed for OTFR beyond what is necessary for initial data processing • Adds negligible time for retrievals • Same operator interface for both pre-archive and OTFR pipelines

  3. OTFR

  4. OTFR • Changes for WFC3? – almost none • ASCII templates for existing instrument processing will be copied and altered to reflect the WFC3 processing locations on disk, and the names of the pipeline processes. • New instrument implies • No keyword repairs yet • No special processing cases yet

More Related