Restructure user guide into focused topic notebooks
@schroedtert ci sta già lavorando.
Dal 28/10/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Summary
Replace the monolithic user guide notebook with a set of focused, topic-specific notebooks and a landing page that explains the overall workflow — including a flowchart — and links to the fundamental diagram notebooks as an end-to-end showcase.
Background / Context
The current user guide is a single large notebook covering all functionality, making it hard to navigate and maintain. Splitting it into focused notebooks improves discoverability and makes it easier to extend. The fundamental diagram notebooks already exist but are not surfaced in the user guide — adding them provides a concrete example of how the individual methods combine into a real analysis.
Technical Details
- Notebooks should be moved to
docs/source/notebooks/so Sphinx can reference them directly without relative path workarounds - The landing page (
docs/source/user_guide/index.rst) should describe the workflow and embed a flowchart - Proposed notebook structure reflecting the typical analysis workflow:
- Measurement Setup — define geometry and measurement regions
- Load Trajectories — import data from various sources
- Preprocessing — (optional) filter and clean data
- Analysis — compute density, speed, flow, and other metrics
- A short notebook explaining how to use pandas for merging, saving (What to do with the results? section)
- The fundamental diagram notebooks serve as the end-to-end showcase tying the above steps together
- The old monolithic
user_guide.ipynbshould be retired once content is distributed
Acceptance Criteria
- User guide landing page exists with a flowchart visualising the analysis workflow
- User guide is split into the four topic notebooks listed above
- Each notebook is self-contained and can be followed independently
- Fundamental diagram notebooks are linked from the user guide as an end-to-end showcase
- Add explanations to Fundamental diagram notebook
- Old monolithic user guide notebook is removed
- ReadTheDocs build renders all notebooks and the landing page correctly
- Lingua principale
- Pascal
- Stelle
- 35
- Fork
- 18
- Merge medio
- 1g 14h
- PR unite (30g)
- 2
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di PedestrianDynamics/PedPy
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 74/100
PedestrianDynamics/PedPy#581 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
PedestrianDynamics/PedPy#580 ·
-
compute_line_flow unitAperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
PedestrianDynamics/PedPy#579 ·
-
Jitter removal with Savitzky-Golay filterForse già presa @awestphal1 l’ha presa 23 giorni fa. Apertapre-processing
PedestrianDynamics/PedPy#578 · 1 assegnatario ·
-
Jitter removal with moving averageForse già presa @awestphal1 l’ha presa 23 giorni fa. Apertapre-processing
PedestrianDynamics/PedPy#577 · 1 assegnatario ·