The calculation model behind the IFS exposure-time calculator, and the transit spectroscopy simulator built on it.
The IFS ETC estimates point-source spectroscopic sensitivity for stellar, SN Ia, or uploaded spectra using the selected spectrograph field and detector configuration.
The extracted spectrum uses an inverse-variance, PSF-weighted point-source variance inside the configured spatial aperture. The headline number is the mean over the selected wavelength interval. The SNR unit selector sets that unit once for the whole calculation, so the requested SNR, the reported SNR, and the plotted curve are always in the same unit. Per pixel is the equation above, one wavelength bin. Per resolution element combines the bins a resolution element spans — 2.3 (CBE) or 2.5 (EOL) — and is therefore higher by √2.3 = 1.52 or √2.5 = 1.58 for the same exposure.
Total throughput actually used by the IFS calculation: the tabulated optical train (throughput_bol.csv for CBE, throughput_eol.csv for EOL) multiplied by the H4RG detector quantum efficiency, for both spectrograph fields. The telescope collecting area is applied separately by the engine and is not folded into these dimensionless curves.
The Transit spectroscopy page answers a different question from the ETC above: not the SNR of one exposure, but how well a transiting planet’s transmission spectrum can be measured with the IFS over one or more transits. It wraps lazuli_exo, which builds the atmosphere model and the host-star spectrum and asks slicersim for the per-wavelength noise.
The depth error per wavelength channel comes from the host star’s SNR in one readout ramp (the IFS ETC calculation, same field, frame time, jitter and background), scaled to the number of ramps that fit in the transit duration t14, with an equal out-of-transit baseline (the √2), and divided by √Ntransits. Channels are then binned to the requested resolving power R. The headline model-vs-flat S/N is the χ-distance between the noiseless model spectrum and a flat (Rp/R*)² line given those errors: a comparison metric for ranking targets and scenarios, not a calibrated detection significance.
Scope and known limitations shared by all three calculators, the installed engine versions, and the link to the observatory documentation are on the site About page.