PlanElement Implementation
PlanElements represent the association of a Plan, a Task,
and a Disposition (where a Disposition is either
an Allocation, an Expansion, an Aggregation, or an AssetTransfer).
A Disposition (as defined above) are subclasses of PlanElement.
PlanElements make a Plan. For Example, a task "move 15 tanks..." with
an Allocation(an Asset, estimated penalty and estimated schedule)
of 15 HETs could represent a PlanElement.
included(Date date) is the Date on or after the start time and strictly before the end time?
boolean whether the date is included in this time interval.
There are four allocation results:
estAR is set by the plugin often as a copy of the reported
rcvAR is computed from downstream results (e.g. by workflow aggregators)
obsAR is set from observed events (event monitor)
repAR is the merge of obsAR and rcvAR and is lazily evaluated
Sets the Task of the PlanElement. This method differs from
setTask in that it is expected that the PlanElement is already
attached to a Task so the Task and PlanElement are rewired
accordingly.
Parameters: t - - The new Task that the PlanElement is referencing.
Set or update the observed AllocationResult. Should be called
only by the event monitor.
Parameters: obsres - the new observed AllocationResult object associated with this pe
CALLED BY INFRASTRUCTURE ONLY - AFTER RESULTS HAVE BEEN COMPUTED ACROSS TASKS.
Parameters: rcvres - the new received AllocationResult object associated with this pe