Skip to content

Speedup testCMCSingleMuscle #1146

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Aug 18, 2016
Merged

Speedup testCMCSingleMuscle #1146

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3615406
Shorten and improve single muscle CMC test. The same model is used, b…
aseth1 Jul 27, 2016
614c905
Added comparison of the muscle force between forward and CMC.
aseth1 Jul 29, 2016
3e02d6b
Turns out that CMC was failing close to the end locally, but was pass…
aseth1 Jul 29, 2016
113bab7
Fixed comment typose
aseth1 Jul 29, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
476 changes: 190 additions & 286 deletions Applications/CMC/test/block_hanging_from_muscle.osim
View file
Open in desktop

Large diffs are not rendered by default.

346 changes: 31 additions & 315 deletions Applications/CMC/test/block_hanging_from_muscle_CMC_Tasks.xml
View file
Open in desktop

Large diffs are not rendered by default.

6 changes: 0 additions & 6 deletions Applications/CMC/test/block_hanging_from_muscle_InitialStates.sto
View file
Open in desktop

This file was deleted.

395 changes: 51 additions & 344 deletions Applications/CMC/test/block_hanging_from_muscle_Setup_CMC.xml
View file
Open in desktop

Large diffs are not rendered by default.

109 changes: 48 additions & 61 deletions Applications/CMC/test/block_hanging_from_muscle_Setup_Forward.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,82 +1,69 @@
<?xml version="1.0" encoding="UTF-8"?>
<OpenSimDocument Version="20302">
<?xml version="1.0" encoding="UTF-8" ?>
<OpenSimDocument Version="30000">
<ForwardTool name="block_hanging_from_muscle">
<defaults/>
<!--Name of the .osim file used to construct a model.-->
<model_file> block_hanging_from_muscle.osim </model_file>
<!--Replace the model's force set with sets specified in
<force_set_files>? If false, the force set is appended to.-->
<replace_force_set> false </replace_force_set>
<model_file>block_hanging_from_muscle.osim</model_file>
<!--Replace the model's force set with sets specified in <force_set_files>? If false, the force set is appended to.-->
<replace_force_set>false</replace_force_set>
<!--List of xml files used to construct an force set for the model.-->
<force_set_files> </force_set_files>
<force_set_files />
<!--Directory used for writing results.-->
<results_directory> block_hanging_from_muscle_ForwardResults </results_directory>
<results_directory>block_hanging_from_muscle_ForwardResults</results_directory>
<!--Output precision. It is 8 by default.-->
<output_precision> 20 </output_precision>
<output_precision>10</output_precision>
<!--Initial time for the simulation.-->
<initial_time> 0.00000000 </initial_time>
<initial_time>0</initial_time>
<!--Final time for the simulation.-->
<final_time> 5.00000000 </final_time>
<!--Flag indicating whether or not to compute equilibrium values for
states other than the coordinates or speeds. For example, equilibrium
muscle fiber lengths or muscle forces.-->
<solve_for_equilibrium_for_auxiliary_states> true </solve_for_equilibrium_for_auxiliary_states>
<final_time>1</final_time>
<!--Flag indicating whether or not to compute equilibrium values for states other than the coordinates or speeds. For example, equilibrium muscle fiber lengths or muscle forces.-->
<solve_for_equilibrium_for_auxiliary_states>true</solve_for_equilibrium_for_auxiliary_states>
<!--Maximum number of integrator steps.-->
<maximum_number_of_integrator_steps> 30000 </maximum_number_of_integrator_steps>
<maximum_number_of_integrator_steps>30000</maximum_number_of_integrator_steps>
<!--Maximum integration step size.-->
<maximum_integrator_step_size> 1.00000000 </maximum_integrator_step_size>
<maximum_integrator_step_size>1</maximum_integrator_step_size>
<!--Minimum integration step size.-->
<minimum_integrator_step_size> 0.00000000 </minimum_integrator_step_size>
<!--Integrator error tolerance. When the error is greater, the integrator
step size is decreased.-->
<integrator_error_tolerance> 0.00001 </integrator_error_tolerance>
<minimum_integrator_step_size>0</minimum_integrator_step_size>
<!--Integrator error tolerance. When the error is greater, the integrator step size is decreased.-->
<integrator_error_tolerance>1e-008</integrator_error_tolerance>
<!--Set of analyses to be run during the investigation.-->
<AnalysisSet name="Analyses">
<objects/>
<groups/>
<objects>
<ForceReporter name="ForceReporter">
<!--Flag (true or false) specifying whether whether on. True by default.-->
<on>true</on>
<!--Start time.-->
<start_time>0</start_time>
<!--End time.-->
<end_time>1</end_time>
<!--Specifies how often to store results during a simulation. More specifically, the interval (a positive integer) specifies how many successful integration steps should be taken before results are recorded again.-->
<step_interval>1</step_interval>
<!--Flag (true or false) indicating whether the results are in degrees or not.-->
<in_degrees>true</in_degrees>
<!--Flag indicating whether to include forces due to constraints.-->
<include_constraint_forces>false</include_constraint_forces>
</ForceReporter>
</objects>
<groups />
</AnalysisSet>
<!--Controller objects in the model.-->
<ControllerSet name="">
<ControllerSet>
<objects>
<ControlSetController name="ControlSetController">
<!--A list of actuators that this controller will control.The keyword ALL
indicates the controller will controll all the acuators in the model-->
<actuator_list> </actuator_list>
<!--Flag (true or false) indicating whether or not the controller is
disabled.-->
<isDisabled> false </isDisabled>
<!--XML file containing the controls for the controlSet.-->
<controls_file> block_hanging_from_muscle_controls.xml </controls_file>
<!--Flag (true or false) indicating whether or not the controller is disabled.-->
<isDisabled>false</isDisabled>
<!--The list of model actuators that this controller will control.The keyword ALL indicates the controller will controll all the acuators in the model-->
<actuator_list></actuator_list>
<!--A Storage (.sto) or an XML control nodes file containing the controls for this controlSet.-->
<controls_file>block_hanging_from_muscle_controls.sto</controls_file>
</ControlSetController>
</objects>
<groups/>
<groups />
</ControllerSet>
<!--XML file (.xml) containing the forces applied to the model as
ExternalLoads.-->
<external_loads_file> </external_loads_file>
<!--Storage file (.sto) containing the initial states for the forward
simulation. This file often contains multiple rows of data, each row
being a time-stamped array of states. The first column contains the
time. The rest of the columns contain the states in the order
appropriate for the model. In a storage file, unlike a motion file
(.mot), non-uniform time spacing is allowed. If the user-specified
initial time for a simulation does not correspond exactly to one of
the time stamps in this file, inerpolation is NOT used because it is
usually necessary to being a simulation from an exact set of states.
Instead, the closest earlier set of states is used. Having a states
file that contains the entire trajectory of a simulations allows for
corrective springs for perturbation analysis to be added.-->
<states_file> </states_file>
<!--Flag (true or false) indicating whether or not the integrator should
use a particular time stepping. If true, the time stepping is
extracted from the initial states file. In this situation, therefore,
the initial states file must contain all the time steps in a
simulation and be written out to high precision (usually 20 decimal
places). Setting this flag to true can be useful when reproducing a
previous forward simulation with as little drift as possible. If this
flag is false, the integrator is left to determine its own time
stepping.-->
<use_specified_dt> false </use_specified_dt>
<!--XML file (.xml) containing the forces applied to the model as ExternalLoads.-->
<external_loads_file />
<!--Storage file (.sto) containing the initial states for the forward simulation. This file often contains multiple rows of data, each row being a time-stamped array of states. The first column contains the time. The rest of the columns contain the states in the order appropriate for the model. In a storage file, unlike a motion file (.mot), non-uniform time spacing is allowed. If the user-specified initial time for a simulation does not correspond exactly to one of the time stamps in this file, inerpolation is NOT used because it is usually necessary to being a simulation from an exact set of states. Instead, the closest earlier set of states is used. Having a states file that contains the entire trajectory of a simulations allows for corrective springs for perturbation analysis to be added.-->
<states_file />
<!--Flag (true or false) indicating whether or not the integrator should use a particular time stepping. If true, the time stepping is extracted from the initial states file. In this situation, therefore, the initial states file must contain all the time steps in a simulation and be written out to high precision (usually 20 decimal places). Setting this flag to true can be useful when reproducing a previous forward simulation with as little drift as possible. If this flag is false, the integrator is left to determine its own time stepping.-->
<use_specified_dt>false</use_specified_dt>
</ForwardTool>
</OpenSimDocument>

Loading