VEDARSHMISHRA

Selected work · 14

JUPITER.

Searching calibrated Cassini images for Jupiter lightning candidates with an explainable computer-vision pipeline, published-event validation, and a structured human-review workflow.

Jupiter project cover
JUPITER
Instrument
Cassini ISS NAC · H-alpha
Search scope
221 images · 9 date windows
Validation
6 of 6 published marks within 8 pixels
Status
Candidate review · no new-lightning claim

Images & documentation

Inside the project.

Published-event validation
01 / 04
Published-event validation

Image evidence for recovery of the published Cassini lightning marks.

From images to review
02 / 04
From images to review

Raw bright regions are filtered into a review pool, not a discovery catalog.

Validation & geometry
03 / 04
Validation & geometry

Pixel recovery and derived surface geometry are separate checks.

Human review
04 / 04
Human review

Structured review separates likely signals, artifacts and uncertain cases.

Method, step by step

From images to evidence.

  1. 01

    Read calibrated images

    Cassini ISS NAC / H-alpha archive products.

  2. 02

    Estimate background

    Contrast stretch and smooth local-background subtraction.

  3. 03

    Find bright regions

    Connected regions above residual SNR 7.

  4. 04

    Measure & filter

    Size, shape, sharpness and SNR; flag tiny pixels, streaks and edges.

  5. 05

    Link nearby frames

    Candidate proximity within 85 pixels and 12 minutes is a review aid.

  6. 06

    Validate & review

    Match published marks; inspect temporal behavior, geometry and human labels.

Evidence, explained

Where the review load comes from.

Review candidates by date window. These are artifact-filtered candidates, not counts of confirmed lightning.

Jupiter review candidates by date2000-12-315652001-01-011,0942001-01-044832001-01-055732001-01-086,3102001-01-093702001-01-104722001-01-114182001-01-132,326

Evidence, explained

From 196,233 bright regions to a reviewable queue.

Different stages answer different questions. A smaller queue is easier to inspect but is not automatically more scientifically accurate.

StageCountInterpretation
Raw connected regions196,233Broad search, including noise and artifacts
Filtered candidates12,6116.43% of raw regions survive review filtering
First-pass review plan106Curated examples, not a random sample or precision estimate
Published validation marks6 / 6Known-reference recovery within eight pixels

Evidence, explained

The detector, without a black box.

These are explicit image-processing rules implemented in Python/NumPy/Pillow.

StageMethodPurpose
Normalize2nd–99.8th percentile contrast stretchBring out weak image structure
Background18 px Gaussian estimate and subtractionSeparate local bright structure from broad background
NoiseMedian absolute deviationRobust residual noise scale
DetectionSNR ≥ 7; eight-neighbor componentsCollect bright connected regions
MeasurementsCentroid, area, integrated/peak SNR, sharpness, elongationPreserve inspectable evidence
Review gateArea ≥ 3 px, peak SNR ≥ 8, no artifact flagsDeprioritize hot pixels, sharp cosmic rays, streaks and borders
Temporal linkingWithin 85 px and 12 minutesRank repeated candidates for review, not confirmation
Future MLAudited positive/negative labels; held-out observation sequencesCompare a learned model against the fixed baseline

Evidence, explained

Date-by-date evidence.

Counts taken from the saved detector summary.

DateImagesRaw regionsReview candidatesKnown matches
2000-12-311250355650
2001-01-0123944710942
2001-01-041738884830
2001-01-052247845730
2001-01-085411564463100
2001-01-091174913700
2001-01-102658804722
2001-01-113167374182
2001-01-13253732723260

Recover known events first

The core question is whether an automated pipeline can recover known published lightning locations in calibrated Cassini ISS H-alpha images. Published marks provide a validation reference before unmatched candidates are considered for further investigation.

An explainable detector

The current detector uses classical computer vision in Python rather than a trained deep-learning model. It estimates local background, detects connected bright regions, and records location, area, signal-to-noise ratio, sharpness and elongation.

Review promotion requires at least three pixels, peak SNR of at least 8 and no artifact flags. Nearby-frame linking helps prioritize inspection but does not prove a persistent lightning event. The ranking score is not a calibrated probability.

Saved search scope

StageCountMeaning
Calibrated frames221Nine date windows
Raw bright regions196,233Broad first-pass detections
Review candidates12,611After artifact filtering
Published marks recovered6 / 6Within an 8-pixel radius
Curated first-pass queue106For structured human review

The processed date windows span December 31, 2000 through January 13, 2001. The saved known-match offsets range from 1.54 to 5.56 pixels. Recovery of six reference marks demonstrates that check only; it does not establish general precision or recall.

Geometry is a separate check

The later saved geometry-validation report covers 106 queue rows: 42 surface coordinates computed, 64 with no surface intersection and zero projection failures. All six published-match candidates have projected coordinates.

Those coordinates are derived metadata from the ISIS camera model. The published reference validates image-pixel recovery, not these latitude/longitude estimates. Coordinate conventions and projection provenance must remain attached, and a shared surface group is not proof of the same storm.

Human review before learning

The 106-row first-pass plan includes six reference positives, 30 temporal-persistence checks, 20 likely artifact examples, 20 strong single-frame checks and 30 lower-priority rows. Reviewers record yes, no or uncertain decisions to build an auditable label set.

A learned classifier remains dependent on sufficient reviewed positive and negative examples. Unmatched review candidates are not confirmed new lightning.

Evidence & limitations

The page summarizes saved detector outputs and review documentation, not a fresh pipeline run. Temporal consistency, artifact rejection, human labels and geometry interpretation remain essential before making scientific discovery claims.

Saved research data
Detection summary · Published-match report

Public source repository

Read the algorithm.

Implementation, configuration, tests and methodology.

Explore source code ↗

Explore more of the work.

← Back to Selected Builds