Home › Forum › SOFA › Using SOFA › [SOLVED] Monitor not exporting data
Tagged: export, Monitor, position, SOFA_2006, Windows_10
- This topic has 1 reply, 1 voice, and was last updated 3 years, 4 months ago by Davacas.
-
AuthorPosts
-
22 July 2021 at 04:28 #20048DavacasBlocked
Hi! I hope you’re all doing well.
I’m currently working on a scene and I would like to track the positions of certain DOFs. This is the line of XML that I’m using for such purpose (I placed it inside the Node tags of the object of interest):
<Monitor name="MonitorCerebro" fileName="./Resultados/SuperficieCerebro" template="Vec3d" listening="true" indices="207 242 266 270 301 355 362 373 906 934" sizeFactor="5" showPositions="true" ExportPositions="true"/>
The other simulation components work fine. However, after running the simulation, the data exported from the monitor does not change through time. Here’s an abstract of the output file:
# Gnuplot File : positions of 10 particle(s) Monitored # 1st Column : time, others : particle(s) number 207 242 266 270 301 355 362 373 906 934 0.01 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507 0.02 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507 0.03 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507 ... 2.89 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507 2.9 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507 2.91 0.387025 5.81145 4.55818 -0.213817 5.66367 4.71812 -0.375827 6.33544 3.54851 1.31797 6.11767 3.39558 1.14221 6.38764 2.42438 -0.633722 6.58522 3.10233 -0.467009 6.74564 2.23766 0.535731 6.8251 1.85116 1.09391 5.84324 4.04853 -0.423748 5.96146 4.11507
As you can see, the data does not change, even though I am moving the objects in the simulation. What am I doing wrong?
19 August 2021 at 01:08 #20183DavacasBlockedI have partially fixed this issue by adding a MeshTopology, MechanicalObject and IdentityMapping component to my collision node. I know these components are mandatory in most scenes, but I hadn’t added them because the carving examples I consulted didn’t use them.
Now I’m having a different problem, which I’ll be discussing in this entry.
-
AuthorPosts
- You must be logged in to reply to this topic.