-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation
Description
We do a few odd(?) things in the simulation config file. For example, the workflows for a given observation, emu
, are described below.
"pipelines": {
"emu":
{
"workflow": "test/data/config/workflow_config_heft_sim.json",
"ingest_demand": 5
},
And the observation information itself is described as follows:
"observations": [
{
"name": "emu",
"start": 1,
"duration": 10,
"instrument_demand": 36,
"data_product_rate": 4
},
The reason for this is as follows:
- Pipelines have an ingest_demand that must be calculated at the same time as we are calculating the values for workflow costs. Thus, the data are related.
- the
"pipelines"
dictionary and the"observations"
dictionary are used in different areas for different reasons; the former being used to generate aWorkflowPlan
within the scheduler, and the latter being used by theInstrument
to dictate when it is occupied.
There are a couple of things like this in the configuration, so it'd be good to have a dictionary of dictionary elements or something to explain this (most likely in the 'configuration' section of the docs).
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation