[BREAKING] name_dof -> name_dofs, Simplified States and Controls methods and and more precise State Dynamics #1033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
UPGRADE GUIDE FROM 3.3.1:
STEP 1
In your dynamic model, if you were declaring
state_configuration,control_configuration,algebraic_configurationorfunctions, they must now be properties of the class and their names must be updated tostate_configuration_functions,control_configuration_functions,algebraic_configuration_functionsandextra_configuration_functionsrespectively.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
nameis now mandatory and should be a property of the class.STEP 4
In your dynamic model, for the class that inherits from
StateDynamicsWithContacts, the fieldcontact_typesis now mandatory as a property and should not be passed anymore to the init method.This change is