Skip to content

Expand terminology glossary and add GLOSSARY.md - #652

Open
ecomodeller wants to merge 4 commits into
mainfrom
docs-terminology-glossary
Open

ecomodeller wants to merge 4 commits into
mainfrom
docs-terminology-glossary

Conversation

@ecomodeller

@ecomodeller ecomodeller commented May 18, 2026 •

Copy link
Copy Markdown
Member

Summary

 docs/user-guide/terminology.qmd      # user-facing
+  Field, Geometry type (gtype), Baseline, Quantity
~  Score: a ComparerCollection concept; Comparer.score is the one-observation case
-  Performance (now an alias under Skill)
~  Observation links → PointObservation / TrackObservation (pointed at model results)
~  Timeseries: point/track vs fields (grid, flexible mesh)
~  "flexible mesh (dfsu)" for the geometry, "dfsu" for the file
~  entries ordered by topic

+GLOSSARY.md                          # dev-facing, domain-modeling format
   Core entities · Geometry types (incl. vertical, network) · Data shapes · Skill assessment

Mesh and file-format terms follow mikeio's glossary.

Evidence

  • Before: the Observation entry linked to PointModelResult / TrackModelResult; no definitions for field, gtype, baseline, quantity, or any network term.
    After: the links go to the observation classes; every gtype in GeometryType has a glossary entry.

Merge Danger

Door: two-way

Docs only.

Blast Radius: docs

🤖 Generated with Claude Code

User-facing terminology page (`docs/user-guide/terminology.qmd`):
- Add Field, Geometry type (gtype), Baseline, and Quantity as first-class entries.
- Reframe Score as primarily a ComparerCollection concept; Comparer.score is the degenerate single-observation case.
- Fold Performance into Skill as an alias instead of a separate entry.
- Fix Observation links that pointed to ModelResult classes.
- Rewrite the Timeseries entry to contrast with fields explicitly (Grid/dfsu are fields, not timeseries).
- Use "flexible mesh (dfsu)" for the geometry concept; keep "dfsu" for the file format. Aligns with mikeio's vocabulary.
- Reorder entries by topic (framing -> data shapes -> matching -> assessment -> abbreviations).

Add a dev-facing `CONTEXT.md` at the repo root that mirrors the user-facing glossary, additionally documents the Vertical alpha vocabulary that is not yet stable for public docs, and records conventions (z-axis direction, dfsu-vs-flexible-mesh, performance-vs-skill, unstructured enum legacy name).
@ecomodeller ecomodeller added the documentation Improvements or additions to documentation label Aug 27, 2026
ecomodeller and others added 2 commits October 22, 2026 13:51
Follows the GLOSSARY.md format: terms, tight definitions and words to
avoid, no implementation details. Adds the network terms (network,
node, reach, break point) that landed since the file was written.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ecomodeller ecomodeller changed the title Expand terminology glossary and add CONTEXT.md Expand terminology glossary and add GLOSSARY.md Oct 22, 2026
Point is CF timeSeries, track is CF trajectory, vertical is CF
timeSeriesProfile. Links mikeio's glossary under its new name.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant