Skip to content

one suggested ranking of interoperability goals #140

@gregtucker

Description

@gregtucker
Building a coupled model from process-oriented software components (models or model elements) - 2


Building “system of systems” models by assembling sub-models of particular systems (for example, a “lake system” model integrated with a “watershed system”) - 3

Operating models/components in multiple different frameworks - 2

Operating models and data inputs/outputs efficiently as part of a sequence of tasks (approach: use/encourage file formats that are both standardized and open) - 1

Swapping input data sources (for example, comparing behavior of a model with two different satellite-based inputs of land cover, as opposed to having the model hard-wired to one particular source) - 1

Controlling parameter values and behavior without recompiling- MINIMAL, 1

Operating a model on multiple platforms - 2

Retrieving information about a model’s current state (including state variables) (implementation question: direct memory exchange vs. file-based exchange vs. web API) - 2

Pausing and continuing model execution - 2

Adjusting model variables and/or control parameters during a run (for example, to support data assimilation) - 2

Computing derivatives where applicable, to facilitate operations such as sensitivity analysis, optimization, and inference (note: different views among participants about whether this should be included in a standard, a “best practice” guideline, or not at all) - 3

Metadata and documentation related to interoperability - 1

    Clarity and precision in definitions of parameters and variables (ontology) - 1/2

    Data items to include in metadata: scale (space and time), typical run time, limits (e.g., range of calibration data) - 1

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions