The current resource implementation allows the user to specify :
- one [upperBound,lowerBound] interval for the initial capacity
- one [upperBound,lowerBound] interval for the valid capacity limits on the
Resource's level at any time
The user should be able to specify a capacity limit profile instead, that
is, a set of tuples {instant,upperBound,lowerBound} that specifies the
capacity limits over time. For instance, if we're modeling a person or a
machine, we should be able to specify intervals where overtime is valid
this way. To deal with situations like overtime, the current approach
requires the user to come up with a max possible upper limit, then lower
the limit with artificial activities to bring capacity down to "normal"
levels. That workaround complicates modeling and app development and has
adverse performance implications.
Also, it seems to be a cleaner modeling interface to have the user set the
capacity at time 0 by a explicit fact in the initial state, instead of
specifying it as "initialCapacity" in the constructor for the resource.
Original issue reported on code.google.com by tristanb...@gmail.com on 9 Sep 2009 at 11:49
Original issue reported on code.google.com by
tristanb...@gmail.com
on 9 Sep 2009 at 11:49