Skip to content

About

Astrobalance — personal-baseline health monitoring for deep-space crews (NASA Space Apps 2026)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Astrobalance — personal-baseline health monitoring for deep-space crews

Tests

NASA Space Apps Challenge 2026 · Challenge: Create Health Monitoring Software for Astronauts on Space Missions (author: Brazilian Space Agency)

Team CosmoMyszki: Jan Domański (backend developer) · Kamila Bąk (frontend developer) · Zuzanna Marciniak (UX/UI designer)

▶ Live app (works offline after the first visit, no login): https://moai-pl.github.io/NASASpaceApps-MoAI/

▶ Demo (7 slides, PDF): docs/demo/Astrobalance-demo-slides.pdf (source: docs/demo/slides/index.html)

Prototype — not medical advice. Model results come from synthetic data calibrated on published sources, plus one alarm-rate check on real everyday data (PMData) and a plausibility check against real astronaut blood tests (NASA OSDR, Inspiration4) — proof of concept, not clinical validation. Not a medical device.

For judges — the 2-minute path

Try it Live app (offline after the first visit, no login): https://moai-pl.github.io/NASASpaceApps-MoAI/
Main result — hold-out S5 (infection onset), a scenario type never seen in development, run once Model detected 10 of 10, median +5 days earlier than fixed clinical limits, with 0.055 false alarms per astronaut-week (clinical limits 0.121). Record: final_test.json (timestamp, commit, config hashes) · table: final_test.md · figure: lead_time_test.png · discussion: 7.3
Model choice Benchmark of 42 configurations at one false-alarm budget: the chosen model catches 71% of simulated changes within 21 days (autoencoders ≤ 59%, clinical limits 44%); 65% → 71% is explained in 7.1
Where it does not win Personal single-value limits alarm ~3.5 days earlier on S5 but with 4.4× the false alarms (7.3)
Real data No alarm in 280 person-weeks of real everyday data (PMData, 7.4) · real NASA DONKI solar events · real Earth–Mars delay per day (NASA/JPL Horizons) · simulator checked against Inspiration4 blood tests (NASA OSDR, 7.6)
Every number's source config_sources.md: each config value is SOURCED or an ASSUMPTION; later-verified sources in config/sources_extra.yaml
Reproduce everything python -m src.run_all (simulate → fit → tune on the selection split → confirm on dev → export → figures; the hold-out is excluded) · pytest -q (runs in CI on Linux and Windows, badge above)
Hold-out discipline src.evaluate --split test --final refuses a second run; tests check that refusal and that the configs still hash to the values recorded with the result (tests/test_holdout.py). The recorded commit 0fc28fe is in the team's first repository, which is not public; the config hashes are the check you can run here (7.3)

1. Overview

Halfway to Mars, “your fellow crew mate feels a sharp pain in the chest and collapses” — the scenario set by the challenge author, the Brazilian Space Agency, in the challenge video (0:43). Our addition: there is no doctor on board, and a message to Earth takes up to ~22 minutes one way.

Astrobalance lets astronauts assess their own health on long missions along two paths:

  • Prevent — an unsupervised model of the personal normal (a multivariate personal-drift model, chosen in a benchmark against autoencoder variants) turns each day's self-measurements into a single Systemic Anomaly Index (SAI, 0–100), with an explanation of which indicators moved and a prompt for the next measurement. The personal normal follows slow, healthy change; on real everyday data (PMData) the model raised no alarm in 280 person-weeks (7.4).
  • Respond — fixed critical thresholds and an emergency mode that work independently of the model, with an escalation ladder that accounts for the communication delay to Earth.

Every NASA Human Research Program hazard is visible in the product:

NASA HRP hazard How Astrobalance covers it Data
Space radiation daily and cumulative absorbed dose, alerts on solar particle events real NASA DONKI SEP events + assumed dose model
Isolation & confinement mind & sleep system (sleep, mood, reaction time); the model detects joint drift synthetic
Distance from Earth escalation ladder and Earth-report queue use the one-way communication delay (for a crew on Mars: the real Earth–Mars light time of each mission day from NASA/JPL Horizons); reports to Earth in SBAR form; comms-blackout mode for Mars solar conjunction config per environment
Gravity fields heart & circulation system (blood pressure, heart rate, exercise) synthetic
Hostile & closed environment cabin CO₂ against the NASA limit; infection onset via temperature and heart rate synthetic

Bone loss cannot be tracked with daily self-measurements and is out of scope (see Limitations).

2. Quick start

conda env create -f environment.yml && conda activate spaceapps   # or, without conda: python -m pip install -r requirements.txt
python -m src.donki --start 2024-05-01 --days 120   # needs internet once: caches real NASA DONKI SEP events
python -m src.horizons --start 2024-05-01 --days 120  # needs internet once: caches the real Earth–Mars delay (JPL Horizons)
python -m src.run_all                               # simulate → fit → tune on bench → confirm on dev → export → figures
python -m src.run_all --benchmark                   # same, plus the model-selection benchmark (~5 min on CPU)
python -m src.robust_bench --window 14              # robustness benchmark: synthetic detection vs real-data alarms (7.5)
pytest -q

The production detector fits in seconds on a laptop CPU; the benchmark trains nine autoencoders (about 30 s each on CPU, --device cuda in src.train for the alternative detector).

Live app: https://moai-pl.github.io/NASASpaceApps-MoAI/ — rebuilt and published by .github/workflows/pages.yml on every push to main. Locally: cd ui/app && npm install && npm run dev, or npm run build for a self-contained static site in ui/app/dist/. The built app is installable and works fully offline after the first visit (own service worker ui/app/public/sw.js, no extra library); check it with npm run preview, then stop the server and reload. UI concept: open ui/concept/index.html in a browser (works offline). See ui/README.md.

The one-time hold-out test is not part of run_all: python -m src.evaluate --split test --final (run once, after freezing config/model.yaml and config/rules.yaml).

3. How it works

  1. Daily check-in — blood pressure, resting heart rate, fasting glucose, temperature, sleep, mood (1–5), reaction time; exercise minutes as context. The six indicators named in the challenge statement are all included. Image-based indicators (camera, ultrasound), which the challenge also allows, are out of scope: Astrobalance uses daily self-measurements only.
  2. Personal normalisation — each indicator is converted to a z-score against that astronaut's own normal, so the model sees deviation from this person's normal, not absolute values. The normal is learned on mission days 1–21 and then follows slow change: a robust exponentially weighted mean that only uses days at least 14 days old (a developing illness cannot be absorbed within two weeks) and moves by at most 2 personal standard deviations per update. An indicator with fewer than 7 values in days 1–21 has no normal yet and is not scored. Exercise minutes are shown as context but not scored (chosen in 7.5).
  3. Drift summary — for each day, the last 14 days are summarised as a weighted mean of the personal z-scores (latest day heaviest), one value per feature.
  4. Personal-drift model (unsupervised) — a Gaussian model of that 9-dimensional summary is learned from 300 healthy simulated astronauts, with no illness labels. The anomaly score is the squared Mahalanobis distance of today's summary from the healthy model (a Hotelling T²-type statistic): it rises when several indicators drift together, even if each one alone still looks normal.
  5. SAI — the percentile of the score among healthy validation days (0–100).
  6. Alert levels — yellow (Watch) when SAI ≥ 94 on 3 consecutive days, orange (Act) when SAI ≥ 99 on 3 consecutive days; a level ends after 7 days in a row below its threshold. P_yellow was tuned on the selection split only, as the most sensitive value with ≤ 0.05 false alarms per astronaut-week. Red comes only from critical thresholds.
  7. Explanation — the score decomposes exactly into one term per indicator (T² = Σ d_f·(Σ⁻¹d)_f); the positive terms give "what moved", mapped to body systems and to the hazard strip; prompts ask for a targeted re-measurement.
  8. Escalation — monitor → self-care → crew medical officer (orange, or yellow for 5 days, or 2+ systems) → flight surgeons (red; on Mars transit the onboard protocol comes first and the report is queued for downlink).

Reference methods the model is compared against:

  • B1 — fixed clinical thresholds (e.g. AHA stage 2 hypertension, ADA hypoglycaemia), 2–3 days persistence.
  • B2 — personal single-indicator thresholds: any indicator beyond 3 personal standard deviations on 2 consecutive days.

4. Architecture

flowchart LR
  A[Daily check-in<br/>manual input / wearables] --> B[Personal normalisation<br/>learned days 1–21, then follows slow change]
  R[Space weather<br/>NASA DONKI SEP] --> H
  C[Cabin CO₂] --> H
  B --> D[14-day drift summary]
  D --> E[Personal-drift model<br/>Mahalanobis vs healthy]
  E --> F[SAI 0–100 + levels]
  A --> G[Critical thresholds<br/>independent of the model]
  F --> H[Local JSON store<br/>offline-first]
  G --> H
  H --> I[Crew UI: SAI, body map,<br/>hazards, prompts, emergency]
  H --> J[Earth report queue<br/>delayed downlink]
Loading

Where things are

Folder What is in it
src/ Python pipeline: simulate (synthetic crews), train (fit the detector), evaluate (selection, confirmation, one-time hold-out), export (JSON for the app), figures; real-data checks realdata (PMData), osdr (NASA OSDR), horizons and donki (NASA data caches)
config/ Every number with its source or assumption: true (frozen for the hold-out); sources_extra.yaml holds sources checked afterwards
data/ raw/ cached NASA data (DONKI, Horizons, OSDR) · real/ PMData daily table · synthetic/demo/ the three demo crew members
outputs/results/ Every result as JSON and Markdown, including final_test.json (hold-out, run once) and config_sources.md
outputs/figures/ Slide-ready figures
outputs/ui/ The JSON contract the app reads (schema in schemas/)
ui/app/ The offline web app (React, Vite, Tailwind), published on GitHub Pages
tests/ pytest suite, run by CI on Linux and Windows
docs/ Demo slides and the project-page texts

5. Why unsupervised

There is no labelled dataset of astronaut illnesses: crews are tiny, serious events are rare and individual health records are private. A supervised classifier has nothing to learn from. A model of each person's normal needs no labels — it only needs healthy days, which every mission produces.

Why not a deep model? We benchmarked it (section 7). On daily data with 9 features, a well-specified statistical model of the healthy state beat every autoencoder variant, including ensembles and per-astronaut fine-tuning. It is also tiny (a 9 × 9 matrix), exactly explainable and trivial to run offline on any flight computer. The autoencoder remains in the code (detector: autoencoder) for richer, higher-frequency data in future work.

6. Data & sources

  • Real data: NASA DONKI solar energetic particle events for the mission window (python -m src.donki). If the cache is missing, no SEP events are simulated and meta.json reports space_weather.status = "missing".
  • Real data: NASA/JPL Horizons ephemeris — Earth–Mars distance for each mission day (python -m src.horizons, cached in data/raw/horizons_earth_mars.json). One-way delay = distance / speed of light: 16.4 min on day 1 falling to 12.1 min on day 120 (Mars approaching Earth); the Sun–Earth–Mars angle stays between 41° and 70°, so this window has no solar conjunction. Used only by the UI for a crew on the Mars surface; the model and simulator never read it.
  • Real everyday data: PMData (Thambawita et al. 2020, CC BY 4.0) — Fitbit resting heart rate, sleep and active minutes plus a daily mood rating from 16 people. The odd-numbered half calibrates the simulator's noise and drift and selects the personal-normal variant (7.5); the even-numbered half is used only to confirm; the model itself is never fitted on it.
  • Synthetic crews (simulator 2): individual astronaut records are privacy-protected, so every astronaut is simulated from config/simulation.yaml. Day-to-day variation is correlated through two latent factors (fatigue, training load); each input's own noise is autocorrelated and every healthy baseline drifts slowly, with both effects estimated from real everyday data (PMData, selection half only: resting heart rate autocorrelation 0.75, drift 0.13 personal sd per √day) and flagged as assumptions where PMData does not measure the input. Scenario sizes were fixed before any evaluation.
Scenario What changes (in personal standard deviations) Role
S1 Cardiovascular deconditioning heart rate +2.5, systolic +2.0, diastolic +1.5, reaction time +0.5; exercise −40 %; 21-day ramp development
S2 Isolation & stress sleep −2.0, mood −2.0, reaction time +2.0, heart rate +1.0; 14-day ramp development
S3 Metabolic disturbance glucose +2.5, sleep −1.0, mood −1.0; 14-day ramp development
S4 Sensor fault one indicator +6 for 5 days development (sensor-fault flag)
S5 Infection onset temperature +2.5, heart rate +2.0, sleep −1.5, mood −1.5, reaction time +1.0; 5-day ramp hold-out test only

Every configuration value is either sourced or flagged as an assumption: full list in outputs/results/config_sources.md (generated by python -m src.report_sources). Sourced values: ISS sleep duration (Barger et al. 2014), CO₂ limit (NASA OCHMO / NASA-STD-3001), blood-pressure categories (AHA), hypoglycaemia levels (ADA), Earth–Mars communication delay (NASA ASCEND). Sources checked after the configs were frozen are kept in config/sources_extra.yaml and listed in the same file, with the values unchanged (the frozen configs belong to the recorded hold-out result): mean body temperature 36.6 °C (Obermeyer et al. 2017) and mean resting heart rate 65 bpm (Quer et al. 2020) are confirmed; day-to-day heart-rate spread is close (3.0 vs our 3.5 bpm); the deep-space dose rate and cabin CO₂ baseline could not be verified in a primary source and stay assumptions.

7. Results

Synthetic data calibrated on published sources — proof of concept, not clinical validation.

Results at a glance

Every number says what data it comes from and how it was tested.

Result Number Data How it was tested
Unseen illness type detected 10 of 10 (clinical limits: 9 of 10; single-value limits: 10 of 10) synthetic, hold-out scenario S5 (infection onset) S5 never looked at during development; evaluated once on the frozen model (commit 0fc28fe)
Earlier than clinical limits +5 days (median; 9 detected by both, 1 more only by the model) same same
False alarms on the same test 0.055 per astronaut-week (clinical limits 0.121, single-value limits 0.241) same same; single-value limits alarm 3.5 days earlier (median) but with 4.4× the false alarms
Changes caught within 21 days at an equal false-alarm budget 71% (fixed personal normal 66%; autoencoders ≤ 59 %; personal single-value limits ≤ 43 %; clinical limits 44 % at their own, higher false-alarm rate) synthetic, selection split (130 astronauts) every method set to 0.05 false alarms per astronaut-week
Alarms on real everyday data 0.000 per person-week — none in 280 person-weeks (fixed normal 0.029; clinical limits 0.021; single-value limits 0.068) real: PMData, 16 people, 4 of 9 inputs no labels: an alarm rate, not accuracy (7.4)

Testing on new people from the same data generator shows that a method generalises to new people. Our hold-out also tests a new type of health change, and the real-data check tests real people.

Protocol. (1) Model selection on a dedicated selection split (bench, new seeds: 30 astronauts per scenario S1–S3 + 40 healthy, scenario sizes × 0.5 and × 1.0), every method tuned to the same false-alarm budget (≤ 0.05 per astronaut-week). (2) Confirmation on the original development split with all thresholds frozen. (3) One run on the hold-out scenario S5 (infection onset), never seen during development; configuration frozen in git commit 0fc28fe before the run.

7.1 Model-selection benchmark

Benchmark

Method family (best variant) Scenarios detected within 21 days Detected at all
Multivariate personal-drift model, 14-day mean (chosen) 65 % 89 %
Drift model + autoencoder ensemble 64 % 87 %
Autoencoder ensemble ×5 (300 training astronauts) 59 % 86 %
Autoencoder, single model (latent distance) 57 % 85 %
Autoencoder + per-astronaut fine-tuning 56 % 81 %
Personal single-indicator thresholds (B2, smoothed) 43 % 74 %
Fixed clinical thresholds (B1, own false-alarm rate 0.106) 44 % 62 %

42 configurations at the 0.05 budget (architecture, training-set size, score components, smoothing, persistence, ensembles, fine-tuning, hybrids): outputs/results/benchmark.md. The second stage (7.5) then chose how the personal normal is kept up to date. The three detection figures in this README are steps on one path, not competing claims: 65% here (stage 1, fixed 21-day normal), 66% for the same fixed normal re-run in the stage-2 grid with its own threshold, and 71% with the adaptive normal finally chosen.

7.2 Confirmation split (thresholds frozen)

Scenario Detected: model / B1 / B2 Median delay after onset (days): model / B1 / B2 Model lead vs B1 (median) Model lead vs B2 (median)
S1 Cardiovascular 100 % / 50 % / 100 % 12 / 24 / 10 +14 d; 5 found only by the model -2 d
S2 Isolation & stress 100 % / 90 % / 100 % 13.5 / 12 / 9.5 +0 d; 1 found only by the model -5 d
S3 Metabolic 100 % / 80 % / 100 % 8 / 18 / 11 +4 d; 2 found only by the model +6.5 d

False alarms per astronaut-week: model 0.065, B1 0.121, B2 0.183. Single-value limits react a few days earlier on S1 and S2, but at about three times the false-alarm rate; at an equal false-alarm budget they catch far fewer changes early (7.1). Small isolation changes (S2 at half size) are the weak spot: 50 % detected (B2 80 %). Full tables: outputs/results/dev_metrics.md.

7.3 Hold-out test — infection onset (S5), evaluated once

Model Fixed clinical thresholds (B1) Personal single-indicator thresholds (B2)
Detected 100 % 90 % 100 %
Median delay after onset 9 days 13 days 4.5 days
Model lead (median) – +5 days (9 detected by both); 1 case found only by the model -3.5 days (all 10)
False alarms per astronaut-week 0.055 0.121 0.241

Hold-out

S5 was never seen during development and was evaluated once (outputs/results/final_test.json, with timestamp and commit hash). The recorded commit 0fc28fe is from the project's first repository, which is not public, so it cannot be opened from here. What can be checked here: final_test.json also records a hash of each frozen config (model, simulator, rules), and the configs in this repository still produce exactly those hashes — tests/test_holdout.py checks this on every push (CI).

What this shows — and what it does not:

  • Against fixed clinical thresholds the hypothesis holds on this synthetic data: earlier detection, including on a scenario type the model never saw, with half the false alarms.
  • Against personal single-indicator thresholds it does not: they alarm about 3.5 days earlier on the infection scenario, but raise 4.4× as many false alarms; on real everyday data they alarm 0.068 times per person-week, the model never (7.4). The trade-off is speed versus a crew that keeps trusting its alerts.
  • The simulator is linear-Gaussian with gradual mean shifts, which favours a Gaussian drift model; on real crew data the ranking could change.

7.4 Real-data check — alarm rate on real everyday data (PMData)

The model was built on synthetic astronauts. To see how it behaves on real human data, we ran it on PMData: 16 people logging Fitbit and wellness data for up to five months (Nov 2019 – Mar 2020; CC BY 4.0). Four of our nine daily inputs exist there — resting heart rate, sleep hours, mood (1–5) and exercise minutes; the others are missing and enter the model as "at your normal". Nothing is fitted on PMData.

Real-data check

Method Alarms per person-week Days in alarm
Astrobalance (adaptive personal normal) 0.000 0%
Same detector with a normal fixed after day 21 0.029 1%
Fixed clinical limits 0.021 0%
Personal single-value limits 0.068 2%

What it shows: the model raised no alarm in 280 person-weeks of real everyday life, where single-value limits alarmed 0.068 times per person-week. The PMData people are not labelled and include winter months, so this is an alarm rate, not accuracy: the model may also have missed real events, and with only 4 of 9 inputs it sees less than it would on a crew.

Data cleaning, fixed before scoring and applied to everyone alike: exercise minutes count as missing on days with no wear evidence (no resting heart rate and no sleep record); sleep records under 1 h or over 16 h are artefacts. Daily table: data/real/pmdata_daily.csv (derived from PMData, CC BY 4.0); output: outputs/results/real_data_check.json; rerun with python -m src.realdata.

7.5 Robustness benchmark — how the personal normal is kept up to date

Real wearable resting heart rate is smoothed (day-to-day autocorrelation ~0.75) and drifts by a few bpm over weeks; a normal fixed after day 21 reads that as deviation. 58 variants of the personal normal and the alarm logic (fixed, rolling, EWMA, robust EWMA, autocorrelation-aware, missing-aware distance, personal score scale, persistence, alarm hold, inputs left out) were compared on the 14-day detector under a rule fixed in advance: each variant's threshold is set on the synthetic selection split to 0.05 false alarms per astronaut-week; among variants whose early detection is at most 5 points below the fixed normal, pick the one with the fewest alarms on half of the PMData people (p01, p03, …); then run it once on the other half and on the dev split.

Model Early detection, synthetic (bench) Real alarms per person-week: selection half → confirmation half Dev false alarms per astronaut-week (benchmark threshold)
Fixed 21-day normal 66% 0.050 → 0.007 0.045
Robust EWMA normal, exercise not scored, alarm held 7 days (chosen) 71% 0.000 → 0.000 0.069

The chosen normal catches more changes early and raises fewer real alarms, at a somewhat higher synthetic false-alarm rate on dev. (The dev column uses each variant's own benchmark threshold; with the production threshold P_yellow = 94 the chosen model has 0.065 false alarms per astronaut-week on dev, 7.2.) Full table and protocol notes (including a missing-data fix made after the first confirmation, and the rounds in which the grid was built): outputs/results/robust_bench.md (python -m src.robust_bench --window 14).

7.6 Plausibility check — simulated glucose vs real astronaut blood tests (NASA OSDR, Inspiration4)

Real astronaut data, used only to compare, never to calibrate: the comprehensive metabolic panel of the four Inspiration4 crew members from NASA OSDR study OSD-575 (Overbey et al. 2024, Nature). Glucose is the one of our nine inputs in that panel; the three pre-flight draws (L-92, L-44, L-3) are compared with the simulator's healthy parameters, which stay frozen.

Real pre-flight draws (4 crew, 12 draws) Simulator (healthy)
Mean (mg/dL) 75.3 (range 56–100) 90
Spread between people (sd) 3.8 8
Spread within a person (sd) 12.6 (draws weeks apart) 6 (day to day)

Partly consistent. The real mean lies inside the simulated healthy population (±2 sd), but 14.7 mg/dL below the simulated mean, and a person's real values vary about twice as much as our day-to-day noise. Caveats: 4 people, 3 draws each, weeks to months apart, fasting state not stated. Post-flight draws are not a healthy baseline and are not compared; three R+45 values below 50 mg/dL are flagged as implausible for healthy people and left uncorrected. The blood count (OSD-569) has no counterpart among our daily inputs and is not used. Table and JSON: outputs/results/osdr_check.md (python -m src.osdr --download, then python -m src.osdr).

Figures (1600 × 900, slide-ready): benchmark.png, lead_time_test.png, lead_time_dev.png, timeline_demo.png (Crew Member Bravo: one false alarm on day 37, model alarm on day 65 after the change starts on day 50, fixed clinical thresholds on day 72), real_data_check.png, healthy_check.png.

8. Earth spin-off

The same offline, personal-baseline monitoring fits isolated crews on Earth: Antarctic research stations wintering without evacuation, remote communities with limited access to care, and long maritime deployments. A personal normal travels with the person; no labelled patient data or constant connectivity is needed. The challenge author names exactly this use — remote communities and places with limited access to health services — in the challenge video.

9. Limitations

  • All astronaut data are synthetic; results show the method works on plausible data, not that it works on real crews. The real-data check (PMData) uses 4 of 9 inputs, is not astronauts and has no labels, so it measures alarm rates, not accuracy.
  • Most simulation parameters are assumptions (listed in config_sources.md); noise and drift are taken from healthy everyday adults, not from spaceflight, and spaceflight adaptation (e.g. fluid shifts) is not modelled.
  • Personal single-indicator thresholds react faster on some scenarios (S1, S2, the S5 hold-out) at several times the false-alarm rate; small isolation changes (S2 at half size) are the model's weakest case.
  • An alarm stays on until 7 quiet days have passed, so a false alarm also lasts longer (9 % of healthy synthetic days in Watch).
  • Daily granularity; no continuous wearable streams (HRV, SpO₂, respiratory rate) — possible future work.
  • Bone loss is not covered (not measurable with daily self-measurements).
  • The emergency-mode steps and the measurement guidance in the app are first-aid and self-measurement guidance paraphrased from the public sources listed in References; they are not a validated medical protocol and do not replace crew medical training or onboard procedures.
  • Model selection used synthetic scenarios designed by the team; the winning model's advantage may partly reflect the linear-Gaussian simulator (see 7.3).
  • Radiation dose values are illustrative; SEP event dates are real only after src.donki has been run with internet access.

10. Use of AI

Generative AI was used in this project, as required to be disclosed by the NASA Space Apps rules:

  • Claude (Anthropic), including via Claude Code, drafted the Python code, tests, configuration files, the concept UI, the figures, this README, the demo slides and the project-page texts (docs/submission.md), and helped search for and verify sources. Every source file carries the header "AI-assisted: drafted with Claude (Anthropic), reviewed by the team".
  • The team defined the concept, made the design decisions, reviewed and ran all code, and checked every cited source.
  • No AI-generated images are used. No NASA logos or branding are used anywhere.

11. References

Data and scientific sources

Crew-facing guidance in the UI app (ui/app/src/content/texts.js; paraphrased and linked, no text copied; checked 2026-11-14)

Software (open-source licenses)

  • Methods: Mahalanobis distance / Hotelling T² statistic (classical multivariate statistics); autoencoders for anomaly detection (benchmarked alternative).
  • Python packages: NumPy (BSD-3-Clause), pandas (BSD-3-Clause), PyTorch (BSD-3-Clause), Matplotlib (Matplotlib license, PSF-based), PyYAML (MIT), Requests (Apache-2.0), jsonschema (MIT), pytest (MIT).
  • Concept UI: React and ReactDOM 18 (MIT, bundled in ui/concept/vendor/), Tailwind CSS 3 (MIT, build time), Babel (MIT, build time).
  • Demo slides (docs/demo/, source docs/demo/slides/index.html): Inter typeface (SIL Open Font License 1.1), embedded in the PDF; screenshots of our own app; background drawn in CSS; QR code to the live app generated with python-qrcode 8.2 (BSD license, used as a tool, not bundled): https://github.com/lincolnloop/python-qrcode
  • UI app (ui/app/): React and ReactDOM 18 (MIT, bundled into the build), Vite 6 (MIT, build time), @vitejs/plugin-react (MIT, build time), Tailwind CSS 4 and @tailwindcss/vite (MIT, build time). No web fonts, icons or images from third parties: system fonts and our own SVG.

12. License and disclaimer

Code and documentation: Apache License 2.0 (LICENSE). This is a research prototype built during a 48-hour hackathon on synthetic data. It is not a medical device, has not been clinically validated and must not be used for medical decisions.

About

Astrobalance — personal-baseline health monitoring for deep-space crews (NASA Space Apps 2026)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages