aligator v0.9.0 #232
ManifoldFR
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version 0.9.0 of aligator brings a host of changes:
Users should assume these changes are API-breaking (in both C++ and Python). Namely:
StageFunctionmethods (e.g.evaluateandcomputeJacobians) now take arguments(x,u), no morey(corresponding to the next state in the OCP);StageDataobjects no longer have the Jacobian fieldStageData::Jy_DynamicsModelclass and its subclasses are no longer subclasses ofStageFunctionfollowing this change. These are now distinct class hierarchiesChecking the changes to the unit tests and examples is recommended.
Known issues
ParallelRiccatiSolverlinear solver is still broken. This requires a more in-depth look, coming in the next version.What's Changed
aligatorby @ManifoldFR in Re-define ALM params struct internally toaligator#219rho_by @ManifoldFR in SolverProxDDP: remove solver parameterrho_#221TrajOptProblemTpl::init_condition_toinit_constraint_by @ManifoldFR in Scale the dynamics' AL parameter instead of the constraints, remove deprecated functions, renameTrajOptProblemTpl::init_condition_toinit_constraint_#223StageConstraint, add option to set dual tolerance onSolverProxDDP, re-implementTrajOptProblemTpl::checkIntegrity()by @ManifoldFR in Deprecate structStageConstraint, add option to set dual tolerance onSolverProxDDP, re-implementTrajOptProblemTpl::checkIntegrity()#226DynamicsModelTplseparate fromStageFunctionTplclass hierarchy by @ManifoldFR in MakeDynamicsModelTplseparate fromStageFunctionTplclass hierarchy #229Full Changelog: v0.8.0...v0.9.0 (commits) | CHANGELOG
This discussion was created from the release aligator v0.9.0.
Beta Was this translation helpful? Give feedback.
All reactions