Is it possible that there are more than one critical path in a
scheduling. MonteCarlo method allows the user to pick up a critical
path from a listbox to do the calculation.
FEA: ItEr63OTS06MonteCarlo
Using a decimal would require that IAllocatable could receive dates as
IntraDayDates instead of LocalDates and this is not supported yet.
FEA: ItEr61OTS04PlanificacionHaciaAtras
* Change field 'End date' (Datebox) in Allocation configuration to 'Workable days' (Decimalbox)
* The field is set first as the difference between task.end - task.start
* Task stores now a new 'workableDays' field that is used when doing the
resource allocations
* Do some UI improvements (rearrange buttons, layout, etc)
FEA: ItEr61OTS04PlanificacionHaciaAtras
* Added configuration option for enabling this menu tab
* Montecarlo method calculates a range of enddates and its corresponding
likelihood. For each task of an order, there are three possible
durations (pessimistic, normal and optimistic). Each duration is
associated with a likelihood value. A montecarlo calculation, generates
for each task a random value and takes the duration of the task
associated to this random value, summing each value for each task, the
resuling value is the hypothetical enddate of that order. This operation
is executed n times. The higher the value, the more accurate the
results, although there is a threshold limit.
FEA: ItEr63OTS06MonteCarlo
Now the mode is changed after hiding the previous tab, so the previous
tab is not repainted and the new tab is showed with the correct mode.
FEA: ItEr63S03BugFixing
Adds a new type of allocating function.
This function allocates hours into resources following a Sigmoid
function.
Known bugs:
* The calendar of a resource (Specific) or the calendar of a Task
(Generic) is not being respected. For instance, the algorithm allocates
hours on bank holidays.
* By default, the algorithm only considers periods of time of 1 hour. If
the calculation estimates an allocation of 0.25 hours for one day, the
result if truncated to 0 hours. This usually happens at the beginning
and at the end of task. Solving the problem at the beginning is easy,
just need to skip allocations with 0 hours assigned, shifting to another
day. But this is not a totally satisfactory solution as it leaves gaps
by the end of the task. To solve this, one solution could be to increase
the period of time by one day at the end, till there won't be 0 hours
allocated on the last day.
FEA: ItEr62OTS04FuncionCurvaS
The combobox for selecting type of assigment function (advance
allocation) is created every time the user changes the zoom
leve
FEA: ItEr62OTS04FuncionCurvaS
Fixed bug, changing the checking if the element is a Task
by an checking if the element is ITaskLeafConstraint,
what permit to move and to update too the milestones.
FEA : ItEr62S05BugFixing
In the future the start will be defined by the aggregate of resource
allocations if the task is planned backwards.
FEA: ItEr62OTS04PlanificacionHaciaAtras
