Lazuli ETC
ETC versions About
Lazuli About

About the Lazuli ETCs

What the Lazuli calculators share: scope and known limits, installed engine versions, and where the instrument documentation lives. Each calculator documents its own model on its About tab.

Instrument guide

The Lazuli ETCs provide observation-planning estimates for three instrument modes. Each result is produced by a separately versioned engine using its installed instrument configuration. A shareable result URL records the resolved form inputs; an exported notebook records the calculation and engine provenance. Each calculator’s model, assumptions and throughput curves are documented on its own About tab: WCC, IFS (including transit spectroscopy) and ESC.

Wide-field imaging
Imaging SNR, source/background count rates, throughput, filter layout, and detector response for selected filter/detector regions.
Integral-field spectroscopy
Exposure/readout configuration and wavelength-dependent SNR for stellar, SN Ia, or custom spectra; transit spectroscopy for exoplanet transmission spectra.
High-contrast coronagraphy
Planet SNR and count-rate contributors as a function of contrast, separation, exposure time, and background assumptions.

Calculator versions

The version shown here is the code currently serving calculations. Result cards and exported notebooks also identify the engine version and source commit used for a run.

WCC wcc_etc v0.1.0
IFS slicersim v1.3.4
IFS lazuli_exo v0.1.2
ESC esc_etc v0.1.0
Interpretation guardrails

Scope and known limitations

Environment

Zodiacal backgrounds are scalar surface-brightness inputs. They are not computed from coordinates, solar elongation, or observing date.

Source spectra

The forms do not apply interstellar extinction. Stellar-library coverage is finite; use a custom spectrum where the available templates are not representative.

Detector effects

Unless explicitly described above, cosmic-ray losses, persistence, correlated 1/f noise, inter-pixel capacitance, brighter-fatter behavior, and charge diffusion are not modeled.

Validity and provenance

Use inputs within the configured instrument domain and treat saturation or calculation warnings as invalidating conditions. Record the engine version, commit, resolved inputs, and configuration with any reported result.