[Hugo]

Thank you very much for your positive feedback @olumide

The need in theoretical background will depend on what you expect to user / achieve / implement.

FEM is definitely a plus and you will have a nice CV for every lab and company in our community! Do not hesitate to let us know if you are looking for something specific.
Best wishes,

Hugo

[Hugo]

hey @peter

could you try still using the downloaded binaries to:
– open SOFA
– open Edit->Plugin Manager
– select the library : in bin/SofaPython.dll provided with the binary of SOFA+SoftRobot for windows

This should work, do not hesitate to keep us posted.
Best,

Hugo

[Hugo]

Dear @arnr

ForceFields in SOFA corresponds to internal or external forces applied on bodies.

I think what you mean would be to modify the SphereForceField so that the center of force would be evolving among time. Is this correct?

If so, it would look like:

// definition of the sphereFF in the scene
typename sofa::component::forcefield::SphereForceField<Vec3d> SphereFF = New<sofa::component::forcefield::SphereForceField>();
m_root->addObject(SphereFF);

...

for( interation loop)
{
    // move at each time step the SphereFF
    SphereFF->setSphere(const Coord& center, Real radius);
}

I hope it helps.
Best,

Hugo

PS: are you working at Kyungpook NUT ?

[Hugo]

hey @ajay

Could you please explain with more details which cmake configure step you are refering to? which version of SOFA are you using? Could you share the error message?

Thx

Hugo

[Hugo]

Hey @nhnhan

would this not be due to the “open” options ?
Have you tried:

  outfile.open("example.txt", std::ios_base::app); // append instead of overwrite

Best

Hugo

[Hugo]

hey @wzdy4444

Your PartialFixedConstraint must be present in the scene graph so that the constraint is properly projected during the animation step. Did you add it in the scene ? Can you share it with us?

Best

Hugo

[Hugo]

hey @jonny

Sorry we are not vision expert on our side.
We had engineers working on such topics like @omar or @bmarques but they left, I don’t if they will still be available to answer you.

Sorry not to help more on this.

Hugo

[Hugo]

Hey @bill757 @fedev @tschuelia

I do not think a function can be directly called from Python. This I will need to check.

However, you could add a ContactListener in your simulation and at each time step using your python script read into the collision information stored in this listener.

I could create a dedicated example in the SofaPython3 plugin in the first week of 2021.

Best,

Hugo

[Hugo]

Hi @mckysd5

At the first look, I would bet on the fact that you are using a FreeMotionAnimationLoop without defining any ConstraintCorrection in the scene. See for example the scene: examples/Components/animationloop/FreeMotionAnimationLoop.scn

(note that the PrecomputedConstraintCorrection requires some precomputation that might take time at first step, but several correction method exist)

Best

Hugo

[Hugo]

Dear @nhnhan

Indeed, in the STLIB plugin, no branch was defined to be compatible with the SOFA release. However, I am pretty sure you can checkout a version of the master of STLIB from July and it would fit the SOFA v20.06 release.

Try for instance in the sources of STLIB:

git checkout 6f2cff8b71652bf8303946c65d881312e516acfc

Hope this helps

Hugo

Hugo

[Hugo]

Hey @andrija987

I have a hard time to understand what you are aiming at.
Do you have any literature, image, scheme of the setup you want to simulate ?

Sorry about it.
Looking forward to reading more about your project.

Best wishes,

Hugo

[Hugo]

Hi @scheikl

Did you already solve this topic?
This comes from a recent PR in master: #1448

@epernod do you have any idea why the default scene now returns this error?

Best

Hugo

[Hugo]

Hi @twxu

It is indeed.
You have the cavity mapped onto a 3D volumetric mesh. The pressure force (if some) applied on your cavity will therefore be interpolated / spread on the connected points on the body mesh as shown by the Mapping lines.

Are you normal well oriented?

Best,

Hugo

[Hugo]

Thanks @scheikl for sharing everything (problem and solution!) on the forum!

Hugo

[Hugo]

I noticed your topic is closed @jonny.
Let us know if you need any further help or if you are willing to share your decision/solution.

Best wishes,

Hugo

[Hugo]

Hi @jonny

Thank you for your question.
Maybe @omar could help on this topic of calibration.

Camera settings use as you do: InteractiveCamera, RecordedCamera, OglViewport (if a new viewport is needed)

<InteractiveCamera name="baseCamera"  position="2.5 5 37.4995"  orientation="-0 -0 0 1"  lookAt="2.5 5 0"  distance="37.4995"  minBBox="-5 0 -8.66"  maxBBox="10 10 8.66"  widthViewport="190"  heightViewport="552" />

You can also use some Camera recorder. You should find an example in examples/Components/visualmodel/RecordedCamera.scn

@froy do you have any idea if there is a way to change the default resolution of the VideoRecorderManager?

Best

Hugo

[Hugo]

Dear @arnr

Could you detail what you mean by changing the center of a forcefield?
Are you talking about a specific forcefield?

Best wishes,

Hugo

[Hugo]

Dear @psimit

Thank you so much for posting your issue AND your solution.
May I ask you to create a pull-request to propose this change back?

Then developers would discuss its integration.

Thanks again.
Best wishes!

Hugo

[Hugo]

Dear @nhnhan

Thank you for your question. It seems you have two un-compatible version:
– what is your SOFA version (20.06 as indicated?)
– what is your STLIB version / branch ?

Best wishes,

Hugo

[Hugo]

Strange. Indeed it seems well loaded.. the second [INFO] is weird.
Any idea @froy? is that related to the recent work on isLoaded?

Hugo

[Hugo]

Ola @fernandov and welcome,

Could you tell us exactly which steps you followed?
Could you give more detail on your error?

Sorry, we need more information to provide support.
Best wishes,

Hugo

[Hugo]

Dear @ajay

What is your SOFA version?
When does the CMake error occur?
Are you building SofaPython3 in or out of tree?

I am sorry, I need a bit more info to help.
Best wishes,

Hugo

[Hugo]

Hi @serkan-ergun

Thank you very much for your interest in our platform for robotics objectives.
Exporting forces and displacement is possible. You can for instance use a VTKExporter.

See an example scene in examples/Components/misc/VTKExporter.scn

Let me know if this is what you are looking for.
Best,

Hugo

[Hugo]

Hey @wzdy4444

Great to read that you are heading towards more and more complicated stuff! Congrats.

in EulerImplicit or EulerExplicit, dofs of previous time steps (i.e. “old positions”) are not stored in the MechanicalObject.
However, you can create your own integration scheme (ODESolver), add a vector and store at each time steps the previous position in this vector.

How to do it would you ask? You can see an example in the RungeKutta4Solver.

The C++ code looks like this:

 
// Allocate auxiliary vectors
MultiVecDeriv oldPos(&vop);
..
oldPos.eq(pos);
..
//then the usual time integration

I hope this helps.
Best

Hugo

[Hugo]

Dear @shan

Great to read it works now.
The error you got with the TetrahedronFEMForceField was due to the fact the mesh loaded was not (or not properly) including tetrahedral elements.

Let me know if you need more information on one of these matters.
Meanwhile, I close the topic. Do not hesitate to open a new one.

Hugo

[Author]

Posts