Hi Radu,

I run the "demo_MCORE_mixerNSC" without encountering the same issues and in 
the end I found the problem. In short, I was calling the function before "
DoStepDynamics()" in the for loop and this was causing the code to crash. 
It is strange because all the other functions like "GetPos()" and 
"GetPosDt2()" work properly in that position outputting "0, 0, 0" at the 
first timestep thus I was expecting the same from "GetAppliedForce()".

Thank you again for your help and patience!

Gianni

Il giorno venerdì 27 dicembre 2024 alle 10:08:18 UTC+1 Radu Serban ha 
scritto:

> Hi Gianni,
>
>  
>
> First of all, which Chrono version are you using? If possible, I suggest 
> using the latest code in the ‘main’ branch of the Chrono GitHub repository 
> since it is a lot easier for us to help resolve issues based on the latest 
> code.
>
>  
>
> Did you try running demo_MCORE_mixerNSC with lines 195-197 
> <https://github.com/projectchrono/chrono/blob/3c8778609d7569c39bcd71a5ebc92c7785c1f09b/src/demos/multicore/demo_MCORE_mixerNSC.cpp#L195>
>  
> uncommented? This works just fine on my end. 
>
> Do you see the same issues with use of these two functions in 
> demo_MCORE_mixerNSC? 
>
> Did you run this through a debugger? That will tell you exactly where and 
> why the code crashes.
>
>  
>
> --Radu
>
>  
>
>  
>
> *From:* [email protected] <[email protected]> *On 
> Behalf Of *Gianni Curti
> *Sent:* Thursday, December 26, 2024 8:53 PM
> *To:* ProjectChrono <[email protected]>
> *Subject:* Re: [chrono] Difference between ChBodyEasyCylinder and 
> AddCylinderGeometry
>
>  
>
> Hi Radu,
>
>  
>
> thank you for your suggestion. In the end it worked by limiting the 
> simulating volume of interest!
>
> Now, I am facing an issue with the command GetAppliedTorque() and 
> GetAppliedForce(). I have defined the ChBody object in my simulation which 
> is subjected to different loads and I need to verify if this ones are in 
> line with what is predicted by theory. However, as soon as I start the 
> application, the simulation crashes without any output error. I am sure 
> that the problem is related to this commands since as soon as I comment 
> them out everything works. Has anybody else ever experienced something 
> similar?
>
>  
>
> Thank you in advance for your help!
>
>  
>
> Gianni
>
> Il giorno lunedì 16 dicembre 2024 alle 13:56:04 UTC+1 Radu Serban ha 
> scritto:
>
> Hi Gianni,
>
>  
>
> Because of the data structures used in Chrono::Multicore, removing 
> elements after system construction is more complicated and expensive, so we 
> opted to not provide this capability.
>
>  
>
> To address the type of issues you are seeing (indeed, as collision shapes 
> move farther and farther apart, the computational cost of the collision 
> broadphase in Chrono::Multicore increases), you can define a region around 
> the computational domain of interest.  With that option enabled, bodies 
> located outside that region will be frozen (in that their state is not 
> updated anymore)
>
> You do that by (1) enabling this option and (2) providing the corners of 
> an axis-aligned bounding box that defines the “active” domain.
>
> An illustration of this setting is in demo_MCORE_mixerNSC 
> <https://urldefense.com/v3/__https:/github.com/projectchrono/chrono/blob/097865c8dd950886be40821aee1f3c13e32bd599/src/demos/multicore/demo_MCORE_mixerNSC.cpp*L167__;Iw!!Mak6IKo!NWIYykk0J_JpErOUAWKzlOz_H7k9k0as68V1h01MLoCSvzv3oI0KYFnLCETYbA9ObRpk4zCrL--GxXF29b_w$>
>  
> in the commented-out lines 168-170.
>
>  
>
> --Radu
>
>  
>
> *From:* [email protected] <[email protected]> *On 
> Behalf Of *Gianni Curti
> *Sent:* Monday, December 16, 2024 12:56 PM
> *To:* ProjectChrono <[email protected]>
> *Subject:* Re: [chrono] Difference between ChBodyEasyCylinder and 
> AddCylinderGeometry
>
>  
>
> Hi Radu and Maksym,
>
>  
>
> thank you for your answer and kindness.
>
> Lately, I was also trying to use the command "RemoveBody()" in the 
> Multicore environment to remove two bodies that falls out of my volume of 
> interest. Otherwise, as they increase their distance from the other bodies, 
> the simulation visibly slows down. However, when I implement this command I 
> get the following error message at the beginning of the simulation.
>
>
> Is there any other way to remove these two bodies from the simulation?
>
> Thanks in advance.
>
>  
>
> Gianni
>
> Il giorno venerdì 29 novembre 2024 alle 13:26:01 UTC+1 Radu Serban ha 
> scritto:
>
> Hi Gianni,
>
>  
>
> ChBodyEasyCylinder creates a body representing a solid cylinder centered 
> at the body COM and aligned along the specified axis of the COM frame.  The 
> body mass and inertia is set automatically assuming the cylinder is solid 
> and has constant density.
>
> AddCylinderGeometry allows you to attach a cylindrical shape (for 
> collision and, optionally also visualization) to an existing body. This 
> utility function allows you to position this cylinder arbitrarily relative 
> to the body COM. This is what “Position on body” represents (a translation 
> of the cylinder shape from the body COM and expressed in the body COM 
> frame.  It is your responsibility to construct the body (including setting 
> its inertial properties).
>
>  
>
> Note that ChBody::SetPos() sets the origin of the body COM frame relative 
> to the absolute coordinate.  It is important to understand well all the 
> frames involved and in what frame various quantities are relative to and 
> expressed in.
>
> See for example the first figure on this Chrono documentation page: 
> https://api.projectchrono.org/development/collisions.html#collision_models_shapes
>  
> <https://urldefense.com/v3/__https:/api.projectchrono.org/development/collisions.html*collision_models_shapes__;Iw!!Mak6IKo!M1N1xkpPgwUX8debhG2NoYwS8xOkXEl2iE_2wA1atPG4NhTpCejq3PBHN_SG2XgrIB7urdtomJ8ChEGod_2e$>
> .
>
>  
>
> --Radu
>
>  
>
> *From:* [email protected] <[email protected]> *On 
> Behalf Of *Gianni Curti
> *Sent:* Wednesday, November 20, 2024 7:26 PM
> *To:* ProjectChrono <[email protected]>
> *Subject:* [chrono] Difference between ChBodyEasyCylinder and 
> AddCylinderGeometry
>
>  
>
> Hi,
>
> I have a question regarding the difference between the commands 
> "ChBodyEasyCylinder" and "AddCylinderGeometry". For what I have understood, 
> the first one automatically calculates the mass and inertia of a body 
> depending on the sizes and density given, while the second one provides 
> only the collision shape of a cylinder (neither mass nor density if they 
> are not manually given). However, I saw that there is the possibility of 
> assigning the "Position on body" when using "AddCylinderGeometry" through a 
> ChVector3d but the result is pretty different from what I obtain by using 
> "SetPos" when I also apply a rotation to the body. What does this command 
> do exactly? 
>
> Thank you in advance for yout patience and kindness.
>
>  
>
> Best Regards
>
>  
>
> Gianni
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion visit 
> https://groups.google.com/d/msgid/projectchrono/10d9deb5-26b4-4ebe-a37b-41e1fdec1037n%40googlegroups.com
>  
> <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/10d9deb5-26b4-4ebe-a37b-41e1fdec1037n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!LZqh0A2nDt0mRsewyds4KGDxAMXR0yiR6uVrKzMnUhhgRxnzpGL_G-mItt0BNX6E85FtgDOxibRx1YgTxMNb$>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
>
> To view this discussion visit 
> https://groups.google.com/d/msgid/projectchrono/a4f47d9a-447f-4b8a-8381-8b0fd3b3efd1n%40googlegroups.com
>  
> <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/a4f47d9a-447f-4b8a-8381-8b0fd3b3efd1n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!M1N1xkpPgwUX8debhG2NoYwS8xOkXEl2iE_2wA1atPG4NhTpCejq3PBHN_SG2XgrIB7urdtomJ8ChAHuzvYP$>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
>
> To view this discussion visit 
> https://groups.google.com/d/msgid/projectchrono/fc0f3582-6d39-419c-a5c5-301f369a9e6en%40googlegroups.com
>  
> <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/fc0f3582-6d39-419c-a5c5-301f369a9e6en*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!NWIYykk0J_JpErOUAWKzlOz_H7k9k0as68V1h01MLoCSvzv3oI0KYFnLCETYbA9ObRpk4zCrL--GxadFmAnZ$>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/projectchrono/26a890e1-caeb-491c-9807-7411248e4442n%40googlegroups.com.

Reply via email to