You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each time the optimal_solve/greedy_solve methods are called, the Request::Model object for each request is initialized during which the invariant battery drain and invariant duration of the request are computed. This makes replanning slow as requests that were planned for before will still need their Models to be generated each time. To make replanning faster, we should maintain a cache of Request::Model within the TaskPlanner
Feature request
Description
Each time the
optimal_solve
/greedy_solve
methods are called, theRequest::Model
object for each request is initialized during which the invariant battery drain and invariant duration of the request are computed. This makes replanning slow as requests that were planned for before will still need theirModels
to be generated each time. To make replanning faster, we should maintain a cache ofRequest::Model
within theTaskPlanner
Implementation considerations
Refer to comment #15 (comment)
The text was updated successfully, but these errors were encountered: