Privacy is good, but sometime things need to be a bit more public. The Custom models are now requiring some public properties to function well. This is more verbose, tidy and open!
NOTE: Here is the migration guide for those who define their own CustomModel
STEP 1
In your dynamic model, if you were declaring state_configuration, control_configuration, algebraic_configuration or functions, they must now be properties of the class and their names must be updated to state_configuration_functions, control_configuration_functions, algebraic_configuration_functions and extra_configuration_functions respectively.
These fields are not mandaroty properties of the dynamic class.
STEP 2
In your dynamic model, the field "name_dof" was changed to "name_dofs" and should now be a property of the class.
STEP 3
In your dynamic model, the field name is now mandatory and should be a property of the class.
STEP 4
In your dynamic model, for the class that inherits from StateDynamicsWithContacts, the field contact_types is now mandatory as a property and should not be passed anymore to the init method.
What's Changed
- [BREAKING] name_dof -> name_dofs, Simplified States and Controls methods and and more precise State Dynamics by @pariterre in #1033
Full Changelog: Release_3.3.1...Release_3.4.0
