A major missing piece in CMB V4 is the ability to explicitly define a task/activity. In V3 things were pretty simple - ModelBuilder could only be used to define a simulation while in V4 ModelBuilder's task of Simulation Construction is loosely modeled:
A major missing piece in CMB V4 is the ability to explicitly define a task/activity. In V3 things were pretty simple - ModelBuilder could only be used to define a simulation while in V4 ModelBuilder's task of Simulation Construction is loosely modeled:
* Which model(s) should be used?
* Which model(s) should be used?
...
@@ -14,6 +14,23 @@ There are a bunch of other tasks that need to be done in a CMB Workflow:
...
@@ -14,6 +14,23 @@ There are a bunch of other tasks that need to be done in a CMB Workflow:
* Model Construction
* Model Construction
* In the multi-scale workflow there are a bunch of model construction tasks
* In the multi-scale workflow there are a bunch of model construction tasks
* Post-processing
* Post-processing
## What is a Task?
A task is a conceptual part of a workflow. In fact a set of tasks is what defines a workflow. Here are some example tasks (and related subtasks):
* Create a Domain for a Surface Water Problem
* Extract boundaries
* Using DEMs or
* Using Imagery
* Fix up Boundaries
* Create domain(s)
* Generate Mesh
* Specify Meshing Parameters
* Run Mesher
* Define a Simulation
* Assign Material Properties to parts of the domain