inverse problems · configuration space what the projection keeps · underdetermined experiments, collapsed configuration spaces, and the tools brought from outside · started October 2026

Method

How this site works

Where it lives, what is generated, how the log is kept, what counts as evidence, and whose the ideas are.

Location

The site is ecosystem/ inside the private repository jmigartua/inverse-problems-configuration-space, next to sources/ (the papers read in full). It has three parts: data/ (YAML: navigation, the brief as theses, the log, the sources), tools/build.py (the generator) and site/ (the Quarto project).

Build

cd ecosystem
python3 tools/build.py        # nav, theses, log page, sources page, home includes, LOG.md
cd site && quarto render      # pre-render runs build.py again, then renders to _site/

The generated files are everything under site/_gen/, site/log/index.qmd and LOG.md. They are not edited by hand.

Publication

Every push to main that touches ecosystem/ runs the Action .github/workflows/publish-site.yml: it builds, checks, renders with Quarto 1.10.18 and replaces the whole content of the public repository inverse-problems-configuration-space-site, which GitHub Pages serves at jmigartua.github.io/inverse-problems-configuration-space-site. The public repository holds no source; the PDFs in sources/ stay private (L002).

The log

data/log.yml holds one entry per dated event: finding entries from reading, decision entries with their reasons and the options set aside, and work entries as the discourse and the programme advance. Ids are L001, L002… in order and never change. A decision is logged the day it is taken.

Evidence

  • Papers. A result is cited to its page, table or figure. The Sources page says of every reference whether it was read here, confirmed by a search, or is cited from memory.
  • Ideas. Each is attributed: Iñigo González de Arrieta's (the brief, T01–T11), Josu's, or this development's. The Discourse page marks the boundary at each step.
  • Words. Structural non-identifiability, practical non-identifiability and model inadequacy are defined once, on the Discourse page, and never used for one another.
  • Code. When a proposal of the programme is taken up, a feature is claimed when its named test passes.

Inherited

The design kit and the build conventions come from diff-ref-struct, and through it from the FTIR ecosystem site of the difes project (L002).