-
Notifications
You must be signed in to change notification settings - Fork 35
Closed
Labels
standards - interoperabilitySuggestions for interoperability standardsSuggestions for interoperability standards
Description
This is an important thing to address, because "model" can mean many things and they are all valid meanings.
Our approach has been to make distinctions in the computational framing of the model, not in the original scientific work. So for example, we distinguish:
- a dataset (eg a soils model)
- a model family (eg MODFLOW: https://www.usgs.gov/mission-areas/water-resources/science/modflow-and-related-programs)
- a model code library (https://www.usgs.gov/software/modflow-2005-usgs-three-dimensional-finite-difference-ground-water-model)
- a model version (eg https://github.com/MODFLOW-USGS/modflow6)
- a model configuration (eg MODFLOW set up with particular processes)
- a model set up (a model that is calibrated/trained for a particular region/context)
- a model run
- a model ensemble
- a model product
- etc.
We also distinguish model types: empirical, theory-based, etc.
Some early publications on this topic (more coming soon): https://doi.org/10.1109/eScience.2018.00132, https://scholarsarchive.byu.edu/iemssconference/2018/Stream-A/11/
Metadata
Metadata
Assignees
Labels
standards - interoperabilitySuggestions for interoperability standardsSuggestions for interoperability standards
Type
Projects
Status
Done