Giter Site home page Giter Site logo

Comments (5)

alda30 avatar alda30 commented on May 29, 2024

By studying some simple examples of ODE I found the answer to the second questions.
At the end of g_callback class, I added this:

if (t>15.5 && t<16) {
        outputData << t << " " << dBodyGetForce(cylinder.m_ODEBody)[2] << " " << dBodyGetLinearVel(cylinder.m_ODEBody)[2] << endl;
}

It writes time, force and its velocity in z direction.
and I just needed the data on the time span between 15.5 to 16 seconds.

from gpusph.

Narcolessico avatar Narcolessico commented on May 29, 2024

Hello,

I would not recommend changing simulation parameters in the gravity callback: it is only designed to return a float3 and changing the simulator parameters might break the consistency of the simulation (e.g. the engine assumes ODE gravity is the same as GPUSPH gravity). Actually, class encapsulation itself should not allow for it.

This being said, it is a smart workaround that anticipates the callback for imposing forces, which is already implemented and will be released soon (sign up to stay up to date ;) ). In case you need to access the force from another part of the code (e.g. making your own Writer class and adding it with given frequency), you can find the resulting force acting on a body in GlobalData::s_hRbTotalForce[device_index][object_index].

from gpusph.

alda30 avatar alda30 commented on May 29, 2024

Thanks Narcolessico for your comment.
When I use GlobalData::s_hRbTotalForce[device_index][object_index] I always get zero in all three directions.
I guess I fill device and object indices incorrectly. Could you help me how to fill them in?
How can I get the index of an specific object in the simulation? or the device? (is the latter cuda related parameter?)
Sorry for asking this, I am a freshman here!


Update: Ok, I think I found out the first parameter is the device number, since I have only one GPU, it should be set to zero, and for the second parameter is the index of rigid body, and again since I have only one rigid body, it should be set to zero again. Now, I have the foces!
Please correct me if I am wrong.

from gpusph.

Narcolessico avatar Narcolessico commented on May 29, 2024

Please note that s_hRbTotalForce only contains the force applied to the body by the fluid, so it should be 0 until the body hits the fluid.

You are correct about the indices of the array.

For any question about the simulator and the API, you're welcome to join #gpusph channel on Freenode.

from gpusph.

alda30 avatar alda30 commented on May 29, 2024

Thanks.
I did so.

from gpusph.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.