1. Single-Galaxy Probe ROTMOD CSV · distance scan · fixed kernel
path: data/rotmod_public/rotmod_csv/<name>
DDO154 / NGC2403 kernel
Waiting for galaxy load…
Points used (finite, err > 0)
–
χ² baseline @ s
–
χ² QDS @ s
–
Δχ² (QDS − base)
–
χ² per point (base)
–
χ² per point (QDS)
–
Best s (QDS scan)
–
χ²QDS(best s)
–
Distance scan plot: χ²QDS(s) vs s.
Best s is marked; lower is better.
2. Multi-Galaxy Summary DDO154 / NGC2403 / NGC3198 / NGC6503 / NGC2841 / NGC7331
uses same kernel + s-range as above
Not run yet. This will load each ROTMOD CSV, scan s, and summarise
“QDS better or worse” at catalog distance and at QDS-preferred s.
| Galaxy | n | Best s | χ²base(s=1) | χ²QDS(s=1) | Δχ²(s=1) | χ²QDS(best s) | Δχ²(best − base) | QDS verdict |
|---|
3. Notes & caveats exploratory · constraint-friendly
- What this page does: takes existing ROTMOD CSVs (rkpc, Vobs, err, Vgas, Vdisk, Vbul), applies a simple Yukawa-like QDS tweak, and lets distance factor s = D / D₀ slide while the kernel stays fixed.
- What it doesn’t do (yet): no inclination, M/L or full beam-smearing fit; those belong in a heavier lab. This one is about “if QDS is right, where would it want this galaxy to sit?”
- How to talk about it: as an offline, falsification-first sandbox. At s = 1 you see whether QDS helps or hurts. The scan then shows whether a modest distance shift could reconcile things, which becomes a testable prediction against independent distance ladders.