coronagraph-comparison · git:20261027.d9f4cba · 2026-10-27 · sha256 4def13d30e7ab24d
coronagraph-comparison git:20261027.d9f4cbaA
Immutable. This exact content never changes and is served at /api/v1/blob/4def13d30e7ab24d.
--- name: coronagraph-comparison description: Compare eclipse observations with K-Cor, SOHO/LASCO and SDO/AIA using independent solar geometry, angular-structure nulls and correctly separated brightness measurements. --- # Compare with coronagraphs Read [setup and operating instructions](../../docs/USAGE.md) before running AEL. Resolve this plugin's root from this skill file and use its bundled launcher. Respond in the user's language. Work on user-selected inputs and write new output directories. Read [the package guide](../../docs/README_AEL.md), [field lessons](../../docs/FIELD_LESSONS.md), and [the comparison template](../../examples/coronagraph_config_template.json). Detailed instrument guidance is in [coronagraph-method.md](../../docs/coronagraph-method.md). Establish which question the data can answer: - Structure: compare angular detail in separate solar frames, with orientation checks and null rotations. A good correlation after radial normalisation does not measure brightness or exclude every local artefact. - Brightness: requires linear, sky-subtracted, extinction-corrected and photometrically calibrated data with uncertainty. A JPEG, filtered layer or display composite cannot be treated as mean solar brightness. Use local reference files when provided. Before downloading observations or calibration tables, state their source, time range, purpose and approximate size and obtain authorization unless that exact download is already authorized. Use the observing date, not the 2026 example date. Reference pixels never enter the user's photograph. Assign a separate `ael.coronagraph.SolarFrame` to each instrument. Preserve affine north/east axes from a plate solution; a pure rotation can be wrong. SOHO's apparent solar radius differs from Earth's. Check metadata, image scale, pylon/occulter masks and angular orientation before trusting a number. Never assume the mirror state of a new camera: count the reflections in the optics (an odd number, as with a star diagonal or a prime-focus astrograph, mirrors the image) and remember that some camera software delivers bottom-up frames. Without stars, a landscape or an annotated frame, scan both mirror states (`ael.coronagraph.scan_mirror`) and decide on the fine detail, never on the whole profile. Report the scan's margin; a second, independent direction is a recommended check when one is at hand, not a reason to hold the result back. Use `coronagraph --config RECIPE --out NEW_DIR` for structure. Report the zero-shift result, orientation search, fine-detail comparison and null maximum, including failures. Brightness work uses the `ael.coronagraph` Python API: K-Cor pB converted through p(r) gives K alone, while a photograph sees K+F; LASCO C2 has alternative published calibrations that must remain distinct. Do not tune a calibration to force agreement. Keep input provenance, hashes, excluded regions, methods and uncertainty. Show diagnostic sheets. State the radius range tested and what remains unvalidated; external agreement is not a global certificate.