nikhilgupta10
commented
7 years ago nikhilgupta10 imported these comments from Sourceforge: "jcfuller": * status changed from new to assigned
- component changed from Unknown to Core
- priority changed from undetermined to critical
- milestone changed from Unscheduled to Version 3.1 RC1
- owner changed from jcfuller to andyfisher
-
type changed from undetermined to validation ,
"dchassin":This fix is similar to climate data interpolation in the sense that it can result in different answers depending on when objects update. A caveat to that effect as been added to the documentation of this feature.,
"dchassin":- Description has changed:
Diff:
- status: assigned --> closed
- Resolution: --> validate
- Component: Core --> core
-
Type: validation --> enhancement ,
"dchassin":The fix is implemented for trunk in ticket 852. This ticket is being closed as a duplicate.,
This change adds a new schedule block option /u2018interpolated/u2019. This causes the schedule to be re-evaluated each sync operation and implements a linear interpolation between schedule values.
This does not change the frequency with which a schedule object will cause a sync operation, but provides an interpolated value if any other object in the model causes a sync operation.
,