Where is the custom property in cu file?

satri
satri Altair Community Member
in Community Q&A

Hello

I am trying to understand this tutorial

image.png

In this tutorial i see that

image.png

When i look at the .cu file provided with the document i do not see the custom properties

image.png

Now, looking at this tutorial, I am getting even more confused. Have you defined the custom property anywhere in the CUDA file, but the tutorial says CUDA custom properties?

I dont know what i should understand from this?

This is what i am trying to do:

I have a custom property1 which i am trying to use with the hertzMindlinAPI-CUDA version.

So, I want to modify this custom property as contacts occur and view it in the GUI during post processing. This custom property will also get added to contactResult.addNormalForce. so tell me this should i do this manuplation of custom property in the cpp file or the cuda file?

Lets say i do it in cpp file. Now my question is should i add the custom property to manuplate the contactResults.normalForce in the Cpp file or in the cuda file?

Please let me know

Tagged:

Answers

  • satri
    satri Altair Community Member

    Hey please let me know how to resolve this. your tutorial does not talk anything about this file called CCohesionV2List.cpp is this required to pass custom properties from cpu to gpu?

    I have put the custom properties in both the cpu cpp file and the gpu cu file. I am constantly seeing the custom property value as 0. When I set up a break point on the CPU file i do not hit that break point at all. Please tell me why this happens?

    I am able to reach the break point in tutorial but the problem is the custom property is not defined in cuda file at all. so i am not sure what is going on and how to interpret this

  • Stephen Cole
    Stephen Cole
    Altair Employee

    The custom properties get added when the model is set in the Creator physics section, this is done via CPU before the simulation starts so only need to be initialised in the cpp. To use they have to be called in the .cu.

    You may not see the break point been hit unless you start debugging before the simulation file is loaded, try attaching the debugger to a blank EDEM instance then opening the file, it should hit the point then.

    Regards

    Stephen

Categories