Open GoogleCodeExporter opened 8 years ago
From Paul:
The Initial Conditions reported by telemetry use case is very important.
In fact, we may need to some capability like this to digest a faulty
execution episode and do replanning. In the AES project, we will be
trying to integrate a diagnostic system with a planning system such as
SPIFE/Europa.
However, I'm not sure specifying upper & lower bound limits captures
this. What is needed is a reset of the state or available amount of
resource at specific fixed times.
Original comment by javier.barreiro@gmail.com
on 6 Oct 2011 at 4:55
the nddl/C++ API that I intend to put in place is something like this:
setLimit(resource,t,newLimitUb,newLimitLb);
that resets the limitUb/Lb starting at time t until the next specified limit
(or until +inf if no other limit bounds are specified). The user can call
setLimit as many times as necessary to fully specify the limit profile, only
piecewise constant profiles will be supported initially.
Paul, if that doesn't seem to address your needs, let's discuss.
Original comment by javier.barreiro@gmail.com
on 6 Oct 2011 at 5:01
Original comment by javier.barreiro@gmail.com
on 12 Oct 2011 at 11:24
Original comment by javier.barreiro@gmail.com
on 30 May 2012 at 5:26
Original issue reported on code.google.com by
javier.barreiro@gmail.com
on 5 Oct 2011 at 8:23