Skip to content

Commit 1f73418

Browse files
alexbeattie42alexbeattie42
committed
Remove unused, legacy <default> blocks in .osim and .xml files
1 parent 20a888b commit 1f73418

File tree

54 files changed

+0
-6774
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+0
-6774
lines changed

‎Models/Hamner/FullBodyModel_Hamner2010_v2_0.osim‎

Lines changed: 0 additions & 119 deletions
Original file line numberDiff line numberDiff line change
@@ -1,125 +1,6 @@
11
<?xml version="1.0" encoding="UTF-8" ?>
22
<OpenSimDocument Version="40000">
33
<Model name="3DGaitModelwithSimpleArms">
4-
<defaults>
5-
<ControlLinear name="default">
6-
<is_model_control>true</is_model_control>
7-
<extrapolate>true</extrapolate>
8-
<default_min>-1</default_min>
9-
<default_max>1</default_max>
10-
<filter_on>false</filter_on>
11-
<use_steps>false</use_steps>
12-
<x_nodes />
13-
<min_nodes />
14-
<max_nodes />
15-
<kp>100</kp>
16-
<kv>20</kv>
17-
</ControlLinear>
18-
<CoordinateActuator name="default">
19-
<!--Name of the generalized coordinate to which the actuator applies.-->
20-
<coordinate>Unassigned</coordinate>
21-
<!--The maximum generalized force produced by this actuator.-->
22-
<optimal_force>300</optimal_force>
23-
</CoordinateActuator>
24-
<PointActuator name="default">
25-
<!--Name of Body to which this actuator is applied.-->
26-
<body></body>
27-
<!--Location of application point; in body frame unless point_is_global=true-->
28-
<point>0 0 0</point>
29-
<!--Interpret point in Ground frame if true; otherwise, body frame.-->
30-
<point_is_global>false</point_is_global>
31-
<!--Force application direction; in body frame unless force_is_global=true.-->
32-
<direction>-1 -0 -0</direction>
33-
<!--Interpret direction in Ground frame if true; otherwise, body frame.-->
34-
<force_is_global>true</force_is_global>
35-
<!--The maximum force produced by this actuator when fully activated.-->
36-
<optimal_force>1000</optimal_force>
37-
</PointActuator>
38-
<TorqueActuator name="default">
39-
<!--Name of Body to which the torque actuator is applied.-->
40-
<bodyA>Unassigned</bodyA>
41-
<!--Name of Body to which the equal and opposite torque is applied.-->
42-
<bodyB>Unassigned</bodyB>
43-
<!--Interpret axis in Ground frame if true; otherwise, body A's frame.-->
44-
<torque_is_global>true</torque_is_global>
45-
<!--Fixed direction about which torque is applied, in Ground or body A frame depending on 'torque_is_global' property.-->
46-
<axis>-1 -0 -0</axis>
47-
<!--The maximum torque produced by this actuator when fully activated.-->
48-
<optimal_force>1</optimal_force>
49-
</TorqueActuator>
50-
<Thelen2003Muscle name="default">
51-
<!--The set of points defining the path of the actuator.-->
52-
<GeometryPath>
53-
<!--The set of points defining the path-->
54-
<PathPointSet>
55-
<objects />
56-
<groups />
57-
</PathPointSet>
58-
<!--The wrap objects that are associated with this path-->
59-
<PathWrapSet>
60-
<objects />
61-
<groups />
62-
</PathWrapSet>
63-
<!--Default appearance attributes for this GeometryPath-->
64-
<Appearance>
65-
<!--The color, (red, green, blue), [0, 1], used to display the geometry. -->
66-
<color>0.80000000000000004 0.10000000000000001 0.10000000000000001</color>
67-
</Appearance>
68-
</GeometryPath>
69-
<!--Maximum isometric force that the fibers can generate-->
70-
<max_isometric_force>546</max_isometric_force>
71-
<!--Optimal length of the muscle fibers-->
72-
<optimal_fiber_length>0.053499999999999999</optimal_fiber_length>
73-
<!--Resting length of the tendon-->
74-
<tendon_slack_length>0.078</tendon_slack_length>
75-
<!--Angle between tendon and fibers at optimal fiber length expressed in radians-->
76-
<pennation_angle_at_optimal>0</pennation_angle_at_optimal>
77-
<!--tendon strain at maximum isometric muscle force-->
78-
<FmaxTendonStrain>0.033000000000000002</FmaxTendonStrain>
79-
<!--passive muscle strain at maximum isometric muscle force-->
80-
<FmaxMuscleStrain>0.59999999999999998</FmaxMuscleStrain>
81-
<!--shape factor for Gaussian active muscle force-length relationship-->
82-
<KshapeActive>0.5</KshapeActive>
83-
<!--exponential shape factor for passive force-length relationship-->
84-
<KshapePassive>4</KshapePassive>
85-
<!--force-velocity shape factor-->
86-
<Af>0.29999999999999999</Af>
87-
<!--maximum normalized lengthening force-->
88-
<Flen>1.8</Flen>
89-
<!--Activation time constant, in seconds-->
90-
<activation_time_constant>0.01</activation_time_constant>
91-
<!--Deactivation time constant, in seconds-->
92-
<deactivation_time_constant>0.040000000000000001</deactivation_time_constant>
93-
</Thelen2003Muscle>
94-
<CMC_Joint name="default">
95-
<!--Flag (true or false) indicating whether or not a task is enabled.-->
96-
<on>false</on>
97-
<!--Weight with which a task is tracked relative to other tasks. To track a task more tightly, make the weight larger.-->
98-
<weight> 1 1 1</weight>
99-
<!--Name of body frame with respect to which a tracking objective is specified. The special name 'center_of_mass' refers to the system center of mass. This property is not used for tracking joint angles.-->
100-
<wrt_body>-1</wrt_body>
101-
<!--Name of body frame in which the tracking objectives are expressed. This property is not used for tracking joint angles.-->
102-
<express_body>-1</express_body>
103-
<!--Array of 3 flags (each true or false) specifying whether a component of a task is active. For example, tracking the trajectory of a point in space could have three components (x,y,z). This allows each of those to be made active (true) or inactive (false). A task for tracking a joint coordinate only has one component.-->
104-
<active>false false false </active>
105-
<!--Position error feedback gain (stiffness). To achieve critical damping of errors, choose kv = 2*sqrt(kp).-->
106-
<kp> 1 1 1</kp>
107-
<!--Velocity error feedback gain (damping). To achieve critical damping of errors, choose kv = 2*sqrt(kp).-->
108-
<kv> 1 1 1</kv>
109-
<!--Feedforward acceleration gain. This is normally set to 1.0, so no gain.-->
110-
<ka> 1 1 1</ka>
111-
<!--Direction vector[3] for component 0 of a task. Joint tasks do not use this property.-->
112-
<r0> 0 0 0</r0>
113-
<!--Direction vector[3] for component 1 of a task. Joint tasks do not use this property.-->
114-
<r1> 0 0 0</r1>
115-
<!--Direction vector[3] for component 2 of a task. Joint tasks do not use this property.-->
116-
<r2> 0 0 0</r2>
117-
<!--Name of the coordinate to be tracked.-->
118-
<coordinate />
119-
<!--Error limit on the tracking accuracy for this coordinate. If the tracking errors approach this limit, the weighting for this coordinate is increased. -->
120-
<limit>0</limit>
121-
</CMC_Joint>
122-
</defaults>
1234
<!--The model's ground reference frame.-->
1245
<Ground name="ground">
1256
<!--The geometry used to display the axes of this Frame.-->

‎Models/Rajagopal/Rajagopal2016.osim‎

Lines changed: 0 additions & 129 deletions
Original file line numberDiff line numberDiff line change
@@ -1,135 +1,6 @@
11
<?xml version="1.0" encoding="UTF-8" ?>
22
<OpenSimDocument Version="40000">
33
<Model name="Rajagopal2016">
4-
<defaults>
5-
<ControlLinear name="default">
6-
<is_model_control>true</is_model_control>
7-
<extrapolate>true</extrapolate>
8-
<default_min>-1</default_min>
9-
<default_max>1</default_max>
10-
<filter_on>false</filter_on>
11-
<use_steps>false</use_steps>
12-
<x_nodes />
13-
<min_nodes />
14-
<max_nodes />
15-
<kp>100</kp>
16-
<kv>20</kv>
17-
</ControlLinear>
18-
<CoordinateActuator name="default">
19-
<!--Flag indicating whether the force is applied or not. If true the forceis applied to the MultibodySystem otherwise the force is not applied.NOTE: Prior to OpenSim 4.0, this behavior was controlled by the 'isDisabled' property, where 'true' meant that force was not being applied. Thus, if 'isDisabled' is true, then 'appliesForce` is false.-->
20-
<appliesForce>true</appliesForce>
21-
<!--Minimum allowed value for control signal. Used primarily when solving for control values.-->
22-
<min_control>-Inf</min_control>
23-
<!--Maximum allowed value for control signal. Used primarily when solving for control values.-->
24-
<max_control>Inf</max_control>
25-
<!--Name of the generalized coordinate to which the actuator applies.-->
26-
<coordinate>Unassigned</coordinate>
27-
<!--The maximum generalized force produced by this actuator.-->
28-
<optimal_force>300</optimal_force>
29-
</CoordinateActuator>
30-
<PointActuator name="default">
31-
<!--Flag indicating whether the force is applied or not. If true the forceis applied to the MultibodySystem otherwise the force is not applied.NOTE: Prior to OpenSim 4.0, this behavior was controlled by the 'isDisabled' property, where 'true' meant that force was not being applied. Thus, if 'isDisabled' is true, then 'appliesForce` is false.-->
32-
<appliesForce>true</appliesForce>
33-
<!--Minimum allowed value for control signal. Used primarily when solving for control values.-->
34-
<min_control>-Inf</min_control>
35-
<!--Maximum allowed value for control signal. Used primarily when solving for control values.-->
36-
<max_control>Inf</max_control>
37-
<!--Name of Body to which this actuator is applied.-->
38-
<body></body>
39-
<!--Location of application point; in body frame unless point_is_global=true-->
40-
<point>0 0 0</point>
41-
<!--Interpret point in Ground frame if true; otherwise, body frame.-->
42-
<point_is_global>false</point_is_global>
43-
<!--Force application direction; in body frame unless force_is_global=true.-->
44-
<direction>-1 -0 -0</direction>
45-
<!--Interpret direction in Ground frame if true; otherwise, body frame.-->
46-
<force_is_global>true</force_is_global>
47-
<!--The maximum force produced by this actuator when fully activated.-->
48-
<optimal_force>1000</optimal_force>
49-
</PointActuator>
50-
<TorqueActuator name="default">
51-
<!--Flag indicating whether the force is applied or not. If true the forceis applied to the MultibodySystem otherwise the force is not applied.NOTE: Prior to OpenSim 4.0, this behavior was controlled by the 'isDisabled' property, where 'true' meant that force was not being applied. Thus, if 'isDisabled' is true, then 'appliesForce` is false.-->
52-
<appliesForce>true</appliesForce>
53-
<!--Minimum allowed value for control signal. Used primarily when solving for control values.-->
54-
<min_control>-Inf</min_control>
55-
<!--Maximum allowed value for control signal. Used primarily when solving for control values.-->
56-
<max_control>Inf</max_control>
57-
<!--Name of Body to which the torque actuator is applied.-->
58-
<bodyA>Unassigned</bodyA>
59-
<!--Name of Body to which the equal and opposite torque is applied.-->
60-
<bodyB>Unassigned</bodyB>
61-
<!--Interpret axis in Ground frame if true; otherwise, body A's frame.-->
62-
<torque_is_global>true</torque_is_global>
63-
<!--Fixed direction about which torque is applied, in Ground or body A frame depending on 'torque_is_global' property.-->
64-
<axis>-1 -0 -0</axis>
65-
<!--The maximum torque produced by this actuator when fully activated.-->
66-
<optimal_force>1</optimal_force>
67-
</TorqueActuator>
68-
<Millard2012EquilibriumMuscle name="default">
69-
<!--Flag indicating whether the force is applied or not. If true the forceis applied to the MultibodySystem otherwise the force is not applied.NOTE: Prior to OpenSim 4.0, this behavior was controlled by the 'isDisabled' property, where 'true' meant that force was not being applied. Thus, if 'isDisabled' is true, then 'appliesForce` is false.-->
70-
<appliesForce>true</appliesForce>
71-
<!--Minimum allowed value for control signal. Used primarily when solving for control values.-->
72-
<min_control>0.01</min_control>
73-
<!--The set of points defining the path of the actuator.-->
74-
<GeometryPath name="geometrypath">
75-
<!--The set of points defining the path-->
76-
<PathPointSet>
77-
<objects />
78-
<groups />
79-
</PathPointSet>
80-
<!--The wrap objects that are associated with this path-->
81-
<PathWrapSet>
82-
<objects />
83-
<groups />
84-
</PathWrapSet>
85-
<!--Default appearance attributes for this GeometryPath-->
86-
<Appearance>
87-
<!--The color, (red, green, blue), [0, 1], used to display the geometry. -->
88-
<color>0.80000000000000004 0.10000000000000001 0.10000000000000001</color>
89-
</Appearance>
90-
</GeometryPath>
91-
<!--The maximum force this actuator can produce.-->
92-
<optimal_force>1</optimal_force>
93-
<!--Maximum isometric force that the fibers can generate-->
94-
<max_isometric_force>546</max_isometric_force>
95-
<!--Optimal length of the muscle fibers-->
96-
<optimal_fiber_length>0.053499999999999999</optimal_fiber_length>
97-
<!--Resting length of the tendon-->
98-
<tendon_slack_length>0.078</tendon_slack_length>
99-
<!--Angle between tendon and fibers at optimal fiber length expressed in radians-->
100-
<pennation_angle_at_optimal>0</pennation_angle_at_optimal>
101-
<!--Maximum contraction velocity of the fibers, in optimal fiberlengths/second-->
102-
<max_contraction_velocity>10</max_contraction_velocity>
103-
</Millard2012EquilibriumMuscle>
104-
<CMC_Joint name="default">
105-
<!--Flag (true or false) indicating whether or not a task is enabled.-->
106-
<on>false</on>
107-
<!--Weight with which a task is tracked relative to other tasks. To track a task more tightly, make the weight larger.-->
108-
<weight> 1 1 1</weight>
109-
<!--Name of body frame with respect to which a tracking objective is specified. The special name 'center_of_mass' refers to the system center of mass. This property is not used for tracking joint angles.-->
110-
<wrt_body>-1</wrt_body>
111-
<!--Name of body frame in which the tracking objectives are expressed. This property is not used for tracking joint angles.-->
112-
<express_body>-1</express_body>
113-
<!--Array of 3 flags (each true or false) specifying whether a component of a task is active. For example, tracking the trajectory of a point in space could have three components (x,y,z). This allows each of those to be made active (true) or inactive (false). A task for tracking a joint coordinate only has one component.-->
114-
<active>false false false </active>
115-
<!--Position error feedback gain (stiffness). To achieve critical damping of errors, choose kv = 2*sqrt(kp).-->
116-
<kp> 1 1 1</kp>
117-
<!--Velocity error feedback gain (damping). To achieve critical damping of errors, choose kv = 2*sqrt(kp).-->
118-
<kv> 1 1 1</kv>
119-
<!--Feedforward acceleration gain. This is normally set to 1.0, so no gain.-->
120-
<ka> 1 1 1</ka>
121-
<!--Direction vector[3] for component 0 of a task. Joint tasks do not use this property.-->
122-
<r0> 0 0 0</r0>
123-
<!--Direction vector[3] for component 1 of a task. Joint tasks do not use this property.-->
124-
<r1> 0 0 0</r1>
125-
<!--Direction vector[3] for component 2 of a task. Joint tasks do not use this property.-->
126-
<r2> 0 0 0</r2>
127-
<!--Name of the coordinate to be tracked.-->
128-
<coordinate />
129-
<!--Error limit on the tracking accuracy for this coordinate. If the tracking errors approach this limit, the weighting for this coordinate is increased. -->
130-
<limit>0</limit>
131-
</CMC_Joint>
132-
</defaults>
1334
<!--The model's ground reference frame.-->
1345
<Ground name="ground">
1356
<!--The geometry used to display the axes of this Frame.-->

0 commit comments

Comments
 (0)