View submitted model outputs based on ION data streams
|Actors||Data Analyst (Registered User), OOI science user (Registered User)|
|Uses||UC.R2.01 Acquire Data From External Dataset
UC.R2.04 Browse to Get Data Product
|Is Used By|
|Is Extended By|
|In Acceptance Scenarios||AS.R2.03A Modelers Integrate External Model with OOI|
|Primary Service||IOOS Integration Package 2|
|UC Status||Mapped + Ready|
This information summarizes the Use Case functionality.
Modeler gets data (pushed) from the Integrated Observatory, runs model, pushes resulting data set(s) into the Integrated Observatory. User can view the resulting data set(s), similarly to any other Integrated Observatory data set. The resulting data set has rich metadata including modeling algorithm and source provenance.
- Modeler's data (to be published to the Integrated Observatory) has been registered in the Integrated Observatory already.
- The model can be submitting data to the Integrated Observatory already (doesn't matter if so).
Model exists and has been registered; a user is interested in discovering and subscribing to it.
- Any OOI science user browses a list of modeler-submitted data sets, chooses a data set and obtains its data identifier.
- Data identifiers can be found using many techniques, the particular one used doesn't matter (can even be by cutting and pasting it).
- Any OOI science user subscribes to the selected modeler-submitted data using data identifier obtained above.
- Now the OOI science user will wait, while the next contribution to the modeler-submitted data set is generated.
- Data is pushed from the Integrated Observatory to an outside operational model run by a Data Analyst.
- 'Outside' means the software is not running on the Integrated Observatory (although that would also work, it isn't the focus of this use case).
- Model reads the data as it arrives.
- Data arrival can trigger the model's execution. (it is not a required step, but a handy way to kick off the activity.)
- The model executes on Data Analyst's local machine, producing derived data (model) artifacts.
- The model's derived output is pushed to the Integrated Observatory through a communication channel previously established.
- Establishment of that channel required registration of the modeler, registration of the model as a data source, definition of the information pushed to ION by the model, and establishment of appropriate metadata to characterize that data stream and data source. See UC.R2.01 Acquire Data From External Dataset.
- Metadata also includes information about the modeling algorithm and the data source's provenance.
- Upon receipt of the model's output, the Integrated Observatory routes it to subscribed parties.
- The OOI science user in the second step receives the data.
OOI science user has received the model outputs.
These comments provide additional context (usually quite technical) for editors of the use case.
Implicitly includes a requirements for modelers to provide rich descriptive metadata. (This will set example for other data providers.)
Deciding whether a new run of the model provides a supplement in a stream, or a new version, is subtle. The optimal default is that each new run is a supplement, unless that run replaces a known faulty run (one that has a bug) – that would be a new version.