-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RTM] Not compute the defects if not in implicit #742
Conversation
Hoping this would decrease the RAM consumption when we are in explicit. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #742 +/- ##
==========================================
- Coverage 81.63% 81.59% -0.04%
==========================================
Files 130 130
Lines 16050 16054 +4
==========================================
- Hits 13103 13100 -3
- Misses 2947 2954 +7
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
@pariterre this one would also be a good candidate to being merge, it will not create merge conflicts I think :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change back to ODE default
Reviewed 4 of 4 files at r1, 2 of 2 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @EveCharbie)
bioptim/dynamics/dynamics_functions.py
line 151 at r2 (raw file):
defects = None # TODO: contacts and fatigue to be handled with implicit dynamics if rigidbody_dynamics is not None:
if rigid != RIGID.ODE:
@pariterre I don't think RigidBodyDynamics.ODE has the same meaning as None, I think it means compute defects = [qdot_from_states_dot - qdot, tau_from_inverse_dynamics - tau] Should I instead create another enum : RigidBodyDynamics.NO_DEFECTS ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 3 files at r3, 2 of 2 files at r4, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @EveCharbie)
Test does not pass on Windows, I will remove it. But here is the Error message for the future: ================================== FAILURES =================================== with_cholesky = False, with_scaling = False
tests\shard3\test_global_stochastic.py:568: bioptim\optimization\optimal_control_program.py:1591: in solve args = ('solver', 'ipopt', {'f': MX(@1=0x1, mac(ones(1x15),vertcat(MINIMIZE_CONTROL(X_scaled_0_0, U_scaled_0_0, @1, S_scaled_...acceptable_constr_viol_tol': 0.01, 'ipopt.acceptable_dual_inf_tol': 10000000000.0, 'ipopt.acceptable_tol': 1e-06, ...})
E RuntimeError: D:\bld\casadi_1685976412967\work\casadi\core\function_internal.cpp:146: Error calling IpoptInterface::init for 'solver': C:\Miniconda3\envs\bioptim\Lib\site-packages\casadi\casadi.py:28956: RuntimeError tests\shard3\test_parameters.py:55 tests\shard3\test_parameters.py:60 tests/shard3/test_global_getting_started.py::test_parameter_optimization[RK4-True] tests/shard3/test_global_getting_started.py::test_parameter_optimization[RK8-True] tests/shard3/test_global_getting_started.py::test_parameter_optimization[COLLOCATION-True] tests/shard3/test_global_symmetrical_torque_driven_ocp.py: 15 warnings tests/shard3/test_global_symmetrical_torque_driven_ocp.py::test_symmetry_by_mapping[RK4-True] tests/shard3/test_graph.py: 16 warnings -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html |
@pariterre can be merged :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 3 files at r5, 1 of 1 files at r6, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @EveCharbie)
All Submissions:
New Feature Submissions:
black . -l120 --exclude "external/*"
)?Changes to Core Features:
This change is