Packages, assumptions, and reference data behind the WCC, IFS, and ESC calculators.
The Lazuli ETCs provide observation-planning estimates for the three instrument modes. Each calculator reports sensitivity and count-rate quantities using the installed backend package version and its current instrument assumptions.
The WCC ETC supports imaging sensitivity estimates across the wide-field filter mosaic. Calculations combine source spectrum or magnitude, sky background, detector/filter selection, aperture radius, jitter, and exposure time to estimate SNR and count-rate terms.
Relevant outputs include source and background count rates, SNR, encircled energy curves, throughput curves, focal-plane/filter layout, and simulated detector images where available. The selected sensor/filter changes both the adopted throughput curve and detector parameters.
The throughputs for the implemented filters are the current best estimate of total filter throughput at the end of life of the mission.
The IFS ETC supports spectroscopic sensitivity estimates over a selected wavelength range. It uses the slicersim backend to model stellar, SN Ia, or custom spectral sources with selected spectrograph mode, bandpass, readout configuration, and guiding assumptions.
Relevant outputs include achieved SNR, exposure time, readout configuration, wavelength-dependent flux and SNR plots, IFS field layout, and exportable spectral data products.
GitHub ->The ESC ETC supports high-contrast exposure-time and SNR estimates for point-source planet detection. Calculations include host-star magnitude, planet contrast or delta magnitude, angular separation, zodiacal and exozodiacal backgrounds, detector noise terms, and post-processing gain.
Relevant outputs include planet SNR, source, sky, speckle, dark-current, and exozodiacal count-rate terms, plus flux/count-rate comparison plots.
GitHub ->These calculators are intended for observation planning and comparative sensitivity estimates. Results depend on the installed backend package versions, instrument configuration files, throughput assumptions, detector parameters, and source/background models. For formal performance estimates, users should confirm the backend package version, git commit, and adopted assumptions reported by the site.
