You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the boundary_collider_desc in FEMVolume method calls renumber_dofs under the hood, which appears to neglect to update the kinematic_nodes, causing the kinematic nodes to be scattered throughout the volume.
Minimal code example:
let mut fem_body = FEMVolumeDesc::cube(5, 2, 2)
.scale(Vector3::new(10.0, 0.5, 0.5))
.young_modulus(1.0e3)
.poisson_ratio(0.2)
.mass_damping(0.2)
.build();
let to_be_kinematized = fem_body.positions().iter().enumerate().filter_map(|(i,p)| {
if i % 3 == 0 && *p == -5.0 {
dbg!(p);
Some(i/3)
} else {
None
}
}).collect::<Vec<_>>();
for i in to_be_kinematized.iter() {
fem_body.set_node_kinematic(*i, true);
}
let co = fem_body.boundary_collider_desc();
{
let pp = fem_body.positions();
dbg!(to_be_kinematized.iter().map(|i| {
[pp[i * 3], pp[i * 3 + 1], pp[i * 3 + 2]]
}).collect::<Vec<_>>());
}
Observe, in the output from dbg!, that the x-coordinates are all over the place.
The text was updated successfully, but these errors were encountered:
werner291
changed the title
FEWVolume renumber_dofs breaks kinematic indices
FE<Volume renumber_dofs breaks kinematic indices
Feb 11, 2021
werner291
changed the title
FE<Volume renumber_dofs breaks kinematic indices
FEMVolume renumber_dofs breaks kinematic indices
Feb 11, 2021
Hello,
the
boundary_collider_desc
inFEMVolume
method callsrenumber_dofs
under the hood, which appears to neglect to update thekinematic_nodes
, causing the kinematic nodes to be scattered throughout the volume.Minimal code example:
Observe, in the output from
dbg!
, that the x-coordinates are all over the place.The text was updated successfully, but these errors were encountered: