You nailed it, I had a problem in my mapping’s
applyJTwhere I was overwriting the output value instead of adding to it, therefore overwriting my ForceField’s contribution. The overall simulation still ran with an explicit solver, albeit with no internal forces, and with a heavy dose of wishful thinking I assumed it worked fine..
I have…[Read more]
Hey @beejay ,
alright then, if the explicit simulation gives you the right behaviour/result (are your sure about it?), then the
addForcefunction is well implemented.
About the implicit simulation:
– are you sure the object is not moving (even small value in the
velocityfield of the
– If so, are you sure to have both the…[Read more]
I have written a custom
ForceFieldand implemented both addForce and addDForce. The simulation runs fine when using an explicit solver, but when I switch to an implicit iterative solver the object is totally rigid and I cannot pull on any vertex. When debugging, the dx input argument to addDForce seems to always be 0.
In case it might…[Read more]
It seems the merge function is only used by
MergeVectors<VecT>::update()(SofaGeneralEngine/MergeVectors.inl). In this case, the
Data<T>& outvariable you see will be of type
Data<VecT>. So, when expending the templates, the
out.push_backis in fact calling
VecT.push_back()since the WriteOnlyAccessor is creating a bridge between
I was looking for copying VectorData and i found the merge function.
Here is the source code of merge function :
/// merging several Data from a VectorData into a large Data (of the same type)[Read more]
static void merge(Data<T>& outputData, const vectorData<T>& vectorData)
size_t nbInput = vectorData.size();
Sorry,Hugo,it doesn’t work, there is not collision response,either.
I did replace the episode
<Node name="Collision">[Read more]
<CylinderGridTopology name="coli" nx="5" ny="5" nz="115" length="21" radius="0.05" axis="1 0 0" />
<BeamLinearMapping isMechanical="true" />
hi,everybody, I am trying to use the BeamFEMModel as a soft catheter and the TriangleTensorMassModel as the deformable model of the tissue; but there is a problem, there is no collision between the catheter model and the soft tissue model, the scn scripts are illustrated bellow:
<?xml version="1.0" ?>[Read more]
<Node name="root" dt="0.01">
Lujain replied to the topic TetrahedralCorotationalFEMForcefeild used with SurfaceRegistration in the forum Using SOFA 4 days, 14 hours ago
Ok I will. And thank you very much!
Hugo replied to the topic TetrahedralCorotationalFEMForcefeild used with SurfaceRegistration in the forum Using SOFA 6 days, 5 hours ago
You have a MechanicalObject that shouldn’t exist:
<Node name="Scene" gravity="0 0 0" dt="0.05" >
<RequiredPlugin name="Registration" pluginName="Registration" />
<VisualStyle displayFlags="showForceFields showVisual" />
<EulerImplicitSolver rayleighStiffness="0.5" rayleighMass="0.5" />
Dear Vincent !
I hope you have a good start with SOFA.
Point by point:
– dimensions: in SOFA, no unit is specified. This means that your 3D models (ex liver) and the physics parameters (ex: Young’s modulus) must be consistent. For instance, if your mesh is in millimeter, your Young’s modulus must be in MegaPascal. Is that clear?
Do not consider…[Read more]
Recently I started collision modelling and have some questions:
– What dimension is one size unit in SOFA? The liver model seems to have size of just under 2 units, a real one is around 150mm, so 1 unit = 0.1m? Gravity constant is defined as 9.81 m/s^2, so is represented in meters instead. Frog model has size 20 units, but haven’t seen a 2 meter…[Read more]
I was looking for a simple representation. I have used a simulated chain of spheres connected via JointSpringForceField to produce a representation of a segment or an artery or vein. I used SkinningMapping for the visual node. This seems to work in general however i do have stability issues at times when the end point of the segment are…[Read more]
Lujain replied to the topic TetrahedralCorotationalFEMForcefeild used with SurfaceRegistration in the forum Using SOFA 1 week, 2 days ago
Here are the scene and data.
To represent blood vessels:
- triangular surfaces are usually used when modeling endovascular catheter navigation, see this paper
- or beams when modeling the vessels as a mechanical structure, see this paper
For the first point, the centerline of vessels can be semi-automatically extracted from medical images, and the triangular…[Read more]
Hugo replied to the topic SofaPhysicsAPI improvements/backward compatibility in the forum Using SOFA 1 week, 3 days ago
This work should soon be available for licensing on the marketplace, stay tuned.
Hugo replied to the topic TetrahedralCorotationalFEMForcefeild used with SurfaceRegistration in the forum Using SOFA 1 week, 3 days ago
Your transfer is no longer available Lujain, could you resend it, please?
- Load More