Observational data engineeringAstrolyte

iris-solar-uv-data

IRIS solar UV observations

Checkpoint 2026-03-25

Image-first IRIS Level 2 workflows with metadata indexing, quicklook generation, ROI comparison, and event-candidate export.

Back to datasetsOpen repository

Lane notes

Current working snapshot

IRIS defines the ingest and indexing backbone: raw Level 2 references stay untouched while per-OBS quicklooks, ROI time series, and event catalogs are produced downstream.

IRIS pair-audit figure with a reference frame, ROI markers, ROI light curves, a threshold line, and frame statistics.

Mirrored proof artifact

Open proof figure

This figure is served from Astrolyte's own public assets so the dataset proof stays accessible even when GitHub file preview or raw delivery is unstable.

Why this artifact

Duplicate-window pair audit artifact

This audit export keeps the reference frame, ROI placement, target-minus-background trace, baseline, threshold, and frame-quality drift visible in one panel for the later 161444 window.

rawFITSprocessedvalidated

Reference figure path

reports/figures/pair_audits/20130903_161444_4202100004__20130903_202024_4202100004/target-second__background-second__20130903_161444_4202100004.png

Validation readout

  • Selected because it exposes image-space inspection and time-series validation in the same artifact.
  • The pair-audit view makes duplicate-window handling inspectable instead of hiding it behind a summary table.

Operational notes

Workflow, outputs, and validation

These notes are served directly from Astrolyte so each lane keeps a stable, browsable checkpoint page independent of upstream GitHub rendering glitches.

Outputs

  • metadata index
  • SJI quicklook outputs
  • ROI time series
  • event candidate catalogs
  • merged event table
  • pair audit outputs

Workflow

  • remote archive query
  • selected observation download
  • metadata indexing
  • quicklook generation
  • ROI comparison
  • event export and pair audit

Validation notes

  • Raw, metadata, derived, and report outputs remain separated instead of collapsing into one folder.
  • obs_dir-aware handling keeps repeated obsid windows from overwriting one another.
  • Pair audits are used to separate auto-ROI drift from actual scene change.