search

Arthlol / bpswg

Automatically exported from code.google.com/p/bpswg
0 stars 0 forks source link

Parameter value change via Calendar #93

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
In the 0.3 specification the parameter has a default value, which is 
overwritten by a parameter change that has a calendar. Potentially overlapping 
calendar durations create complexity of which value is active and when to 
reapply the default value.

For usability and comprehension the concept of changing a parameter value at a 
point in time is simpler than having a calendar with duration for when the 
specific value is applicable.

ACTION: suggest we adopt the 'point in time' overwrite as opposed to the 
applicability based on a duration.

Original issue reported on code.google.com by jhor...@lanner.co.uk on 3 Jul 2012 at 10:01

GoogleCodeExporter commented 9 years ago 
As discussed on the July 19th call. My issue with that proposal of flipping 
values on time points is that the default value is unclear.

There need to be a value before we hit the first time point to change that 
value. The problem is depending when the simulation is started, that default 
value would be different.

ex:

Lets consider a monday to friday work schedule from 9am-5pm. It would be 
expressed as 2 time points:
   -Every Week Day at 9am set the value to B
   -Every Week Day at 5pm set the value to A

If you start this simulation on sunday night, the default value implied would 
be A but if you start this simulation on monday at 1pm, it would need to be B.

To determine the initial value of parametes, it would be very complex and just 
adding a default value would not work because it depends when you start the 
simulation.

Original comment by sringue...@trisotech.com on 19 Jul 2012 at 3:09

GoogleCodeExporter commented 9 years ago 
A way of managing overlapping calendar periods is explained in the attached 
document. If we adopt this we have a good method for using the the full 
iCalendar with Duration.

Please see attached file.

Original comment by jhor...@lanner.co.uk on 24 Jul 2012 at 8:59

Attachments:

GoogleCodeExporter commented 9 years ago 
It was decided on the October 11th call that this issue would be parked for 
version 1.0 and we would keep the actual calendar implementation

Original comment by sringue...@trisotech.com on 11 Oct 2012 at 7:15