Tasks Manager
The GEOS tasks manager allows a user to specify tasks to be executed. These tasks are compatible targets for the Event Management.
The tasks manager is configured via the Tasks
block in an input .xml file, i.e.:
<Tasks>
<PackCollection name="historyCollection" objectPath="nodeManager" fieldName="Velocity" />
</Tasks>
Tasks Manager Configuration
Task
The children of the Tasks block define different Tasks to be triggered by events specified in the Event Management during the execution of the simulation. At present the only supported task is the PackCollection
used to collect time history data for output by a TimeHistory output.
Name |
Type |
Default |
Description |
---|---|---|---|
CellToCellDataCollection |
node |
||
CompositionalMultiphaseReservoirPoromechanicsInitialization |
node |
XML Element: CompositionalMultiphaseReservoirPoromechanicsInitialization |
|
CompositionalMultiphaseStatistics |
node |
||
HydrofractureInitialization |
node |
||
MultiphasePoromechanicsInitialization |
node |
||
PVTDriver |
node |
||
PackCollection |
node |
||
ReactiveFluidDriver |
node |
||
RelpermDriver |
node |
||
SinglePhasePoromechanicsConformingFracturesInitialization |
node |
XML Element: SinglePhasePoromechanicsConformingFracturesInitialization |
|
SinglePhasePoromechanicsEmbeddedFracturesInitialization |
node |
XML Element: SinglePhasePoromechanicsEmbeddedFracturesInitialization |
|
SinglePhasePoromechanicsInitialization |
node |
||
SinglePhaseReservoirPoromechanicsConformingFracturesInitialization |
node |
XML Element: SinglePhaseReservoirPoromechanicsConformingFracturesInitialization |
|
SinglePhaseReservoirPoromechanicsInitialization |
node |
XML Element: SinglePhaseReservoirPoromechanicsInitialization |
|
SinglePhaseStatistics |
node |
||
SolidMechanicsStateReset |
node |
||
SolidMechanicsStatistics |
node |
||
SourceFluxStatistics |
node |
||
TriaxialDriver |
node |
PackCollection
The PackCollection
Task is used to collect time history information from fields. Either the entire field or specified named sets of indices in the field can be collected.
Name |
Type |
Default |
Description |
---|---|---|---|
disableCoordCollection |
integer |
0 |
Whether or not to create coordinate meta-collectors if collected objects are mesh objects. |
fieldName |
groupNameRef |
required |
The name of the (packable) field associated with the specified object to retrieve data from |
name |
groupName |
required |
A name is required for any non-unique nodes |
objectPath |
groupNameRef |
required |
The name of the object from which to retrieve field values. |
onlyOnSetChange |
integer |
0 |
Whether or not to only collect when the collected sets of indices change in any way. |
setNames |
groupNameRef_array |
{} |
The set(s) for which to retrieve data. |
Note: The time history information collected via this task is buffered internally until it is output by a linked TimeHistory Output.
Triggering the Tasks
Tasks can be triggered using the Event Management.
Recurring tasks sould use a <PeriodicEvent>
and one-time tasks should use a <SoloEvent>:
<PeriodicEvent name="historyCollectEvent"
timeFrequency="1.0"
targetExactTimeset="1"
target="/Tasks/historyCollection" />
The keyword target
has to match the name
of a Task specified as a child of the <Tasks>
block.