Sun spectrum model — contributor reference
The Light & Sun lens reconstructs solar spectral irradiance and convolves it through published action spectra to derive per-channel doses. This page documents the model, the action spectra, and the calibration choices for anyone touchingjs/sun-spectrum.js or js/sun-uvdata.js.
Pipeline
Wavelength grid
Action spectra (per channel)
Each channel has a closed-form action spectrum function returning a 0–1 weighting per nm. Defined injs/sun-spectrum.js:
The CCO action spectrum (
ccoAt) in the file is an unused helper that sums Karu’s four absorption bands; PBM channels use the simpler narrowband Gaussians for cleaner therapy-device dose math.
The citation registry is duplicated in data/sun-action-spectra.json for AI context grounding.
Bird-Riordan reconstruction
Implemented asreconstructSpectrum() with these terms per wavelength:
- E0(λ) — extraterrestrial spectral irradiance, hardcoded fit to ASTM E490 reference at sample points 280, 300, 320, 340, 360, 380, 400, 420, 450, 500, 550, 600, 650, 700, 800, 900, 1000, 1200, 1500, 2000, 2500 nm with linear interpolation between
- T_Rayleigh —
exp(-tauR × airMass)withtauR = altScale / (λ´ × (115.6406 - 1.335/λ²)),λ = nm/1000, andaltScale = exp(-altitudeM / 8000) - T_O3 —
exp(-ozoneAbsorption(nm) × airMass × ozoneDU/1000)with Bass-Paur cross-section approximation peaking in the Hartley band (~250 nm) - T_aerosol —
exp(-tauA × airMass)withtauA = beta × (nm/500)^-1.14;betauses a positive supplied AOD value or the0.10fallback - cloudT —
1 - 0.75 × cloudCover(linear cloud transmission) - airMass —
1 / max(cos(zenithDeg × π/180), 0.001)
Channel dose calculation
gain is:
- Whole-body skin-yield proxies (
vitamin_d,pomc,no_cv) →skinIrradianceMultiplier × bodyExposureFraction - Local skin-fluence channels (
nir_solar,pbm_red,pbm_nir) →skinIrradianceMultiplierwhen any body exposure is logged; they do not shrink with the size of the treated patch - Eye channels (circadian, violet_eye) →
eyeMultiplier(eyeExposure):direct + clear→ 1.0clear-glasses→ 0.85 (blocks UV, passes visible)glass-window→ 0.4 (passes most visible, blocks NIR + UV)polarized→ 0.5photochromic→ 0.3blue-blocker→ 0.4amber/red→ 0.2sunglasses→ 0.05closed-eyes,indoor→ 0
eyeExposure is null (no eye exposure logged). Skin channels are unaffected by eye-mode.
Genetic vitamin D context
geneticVitaminDMultiplier(genetics) reads four catalog calls and returns a compound multiplier plus an auditable contributor list:
vitaminDIURaw() multiplies the channel result by this compound value before the per-session and daily caps are applied. Missing or reference calls contribute 1.0.
These are conservative heuristic weights for associations with circulating 25-OH vitamin D. They are not genotype-specific intervention responses and do not directly measure skin synthesis, transport, hydroxylation, or personal blood response. The UI therefore describes an effective serum response per modeled UV dose, not genetically calculated vitamin D production.
VDR rs2228570 and CYP27B1 rs10877012 remain in the public Genome catalog as informational/mechanistic context but are intentionally excluded from the multiplier because their cited studies do not establish a change in circulating 25-OH vitamin D or UV response. Claim scopes and publication links live in data/snp-health.json.
Safety counters
Two safety counters are computed alongside the channel doses:Erythemal SED
{ I: 2, II: 2.5, III: 3, IV: 4.5, V: 6, VI: 10 }.
Burn-risk is cumulativeMEDToday() (sum across all sessions today).
Ocular actinic UV
direct and wavelength-attenuated glass-window paths. It represents incident anterior-eye actinic UV, not retinal dose and not the visible or thermal hazard of looking at the sun. The legacy export name retinalUVdose aliases this function for stored/session compatibility only. It is a safety counter and is never recommended to maximize.
Legacy normalization anchors
CHANNEL_DISPLAY[k].dailyTarget remains an internal compatibility anchor used by older tiered records and correlation helpers:
Legacy helpers map these anchors through the following tier function:
weeklyChannelTier() uses the same ratios with a sevenfold anchor for older seven-day rollups.
These values are not literature-established personal requirements, treatment doses, or user goals. The current channel UI must not expose percentages, deficiency, sufficiency, completion, or progress against them. It shows whether sunlight and/or a device signal was logged, the source split, and a seven-day rhythm. AI prompts carry the same rule: missing logs are missing data, not missing biology.
Adding a new channel
- Add an entry to
CHANNEL_DISPLAYinjs/sun.jswithicon,label,dailyTarget, andwhat(user-facing tooltip) - Add an action-spectrum function to
js/sun-spectrum.js - Append to the
CHANNELSarray in the same file with{ id, key, fn, label } - Add a row to
data/sun-action-spectra.json’schannelsblock with the citation - Add to the dashboard pill order in
js/views.jsand the page/detail render order injs/light-channel-view.js - Update
js/sun-correlations.jsif the channel should be biomarker-correlated - Update
tests/test-sun-spectrum.js— assert the channel is inSUN_CHANNELSand has non-zero dose at noon
UV data source
js/sun-uvdata.js resolves the active UV data provider via providerOrder(cfg):
Legacy
cams, noaa, and manual modes auto-migrate to auto in getMeteoConfig(). The current picker exposes only Auto, Open-Meteo, and Self-hosted.
CAMS compatibility operation: official clients send the fixed CAMS payload to https://integrations.getbased.health/api/proxy; independent deployments use same-origin /api/proxy. The operated relay forces latitude and longitude to a 0.1° grid even if a client sends more precision, injects the fixed upstream bearer, and returns a bounded atmosphere envelope. The browser applies the same rounding before a direct Open-Meteo fallback. Self-hosters can run a compatible source and select Self-hosted.
The relay does not expose a server-side /spectrum reconstruction. It returns atmosphere data; reconstructSpectrum() always runs in the browser. CAMS-McRad surface UV remains out of scope because its queue/pre-registered-location model does not fit synchronous per-coordinate requests.
Source confidence is computed at read time from source, snapshot age, cloud cover, sun elevation, UVI band, and staleness. It is an uncertainty signal for the modeled input, not radiometer accuracy. Do not restore the retired manual-source shortcut or assign perfect confidence to a user-entered UVI: one value cannot supply the full atmosphere/spectrum model.
Validation
tests/test-sun-spectrum.js covers ~120 assertions:
- Spectrum shape (wavelength array, 5nm grid, 280–2500 nm bounds, non-negative irradiance)
- Sun-below-horizon → all-zero spectrum
- Atmospheric attenuation (zenith / ozone / cloud / altitude) — directional checks
- Channel dose calculation (all channels, body fraction scaling, eye-mode gating, sunglasses → near-zero circadian)
- Safety counters (SED scales linearly with duration, Fitzpatrick I reaches its reference before VI, ocular actinic UV is weighted and gated by eye/glass conditions)
- Edge cases (night spectrum, zero-duration session)