Java Doc for VishnuAggregatorPlugin.java in  » Science » Cougaar12_4 » org » cougaar » lib » vishnu » client » Java Source Code / Java DocumentationJava Source Code and Java Documentation

The key thing to note is that the asset in the task->asset
association is on the WITH preposition of the generated MPTask.

This is critical, because the allocator downstream will look for this
prep and pluck the asset off to make the allocation.

Uses the assigned start and end times to set the preferences and
allocation results.

Adjust preferences so that the start time preference is the assigned
start time, and the end time preference has a best date that is the
assigned end time. The early and late dates of the end time preference
are the same as the first parent task. (This isn't very important, as the
downstream allocator should just allocate to the start and best times.)

Many times subclasses will want to redefine
interestingTask and interestingAsset to filter
what goes to the Vishnu scheduler. If you do, it's good form to call
super.interestingTask().

See Also:   org.cougaar.lib.vishnu.client.VishnuPlugin.interestingAsset
See Also:   

 Defines how the MPTask holds the asset for the task->asset association.

 Background : the missions for a conveyance (ship, plane, truck)
 are represented by MPTasks which assign an asset group of items
 to a conveyance for a certain period of time.

If there is a quantity preference on the first task, will calculate an aggregate
quantity preference. Assumes then that all tasks will have a quantity pref.
Parameters:
  a - - the asset associated with the MPTask
Parameters:
  g - - parent task list
Parameters:
  start - - the date for the START_TIME preference
Parameters:
  end - - the best date for the END_TIME preference Vector - list of preferences for the MPTask

 Defines how the MPTask holds the asset for the task->asset association.
 Should be in sync with getAssetFromMPTask, which accesses the prep.
 Critical, because the allocator downstream will look for this prep and
 pluck the asset off to make the allocation.
 

 Background : the missions for a conveyance (ship, plane, truck)
 are represented by MPTasks which assign an asset group of items
 to a conveyance for a certain period of time.  We want to prevent
 the case where multiple MPTasks together represent one actual
 mission, i.e. they are for the same conveyance and the same period 
 of time.  It's better for memory footprint, simplicity, and the
 asset usage display in the TPFDD Viewer.
 See bug #11866 : https://bugs.ultralog.net/show_bug.cgi?id=11866
 Makes an aggregation given a list of assignments.
 Makes an aggregation with a medium confidence and publishes it.  
 Also makes an expansion of the MPTask.  This may be a 1-to-1,
 1-to-2, or 1-to-3 expansion depending on the dates.  If the
 setup start is before the task start, then a separate setup task
 is created and added to the expansion.  Similarly for wrapup.
 These dates are different if the vishnu scheduling specs define
 setup (e.g. fueling an airplane) or wrapup (e.g. servicing an airplane)
 durations.  See referenced Vishnu documentation for details on specs.
 Calls the base class function makeSetupWrapupExpansion.
 Adds to a previously created MPTask when new tasks are assigned to an
 asset.