🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

How to use EDEMpy to edit particle properties.

User: "VikiZhang"
Altair Community Member

Dear all,

I'm having some trouble using EDEMpy to control particle movement in my simulations and would appreciate any advice.

I've encountered two main problems:

  1. The particle velocity and position values I get from EDEMpy (using deck.timestep.particle.getXVelocities() and getPositions()) don't match what I see in the EDEM UI, even though the simulation setup looks correct.
  2. When I try to modify particle properties using deck.setParticleVelocity or deck.setParticlePosition, I keep getting an error about "le id" even though I'm sure the particle ID is correct.

Has anyone experienced similar issues? Any suggestions on what might be causing these problems or how to fix them?

Thanks a lot your help.

Regards,

Viki

Find more posts tagged with

Sort by:
1 - 2 of 21
    User: "Renan"
    Altair Employee

    Hi Viki,

    Could you please share the code you're using and the error messages you're getting? This will help me identify the most probable cause more easily.

    Best regards,

    Renan

    User: "VikiZhang"
    Altair Community Member
    OP
    Updated by VikiZhang

    Thanks for Renan’s reply.

    Here I attached two pictures. The first picture shows my first question:

    Values in table (output by EDEM UI) show that velocities in xyz axies are around O(n^-3), but EDEMpy tells that they are around O(n^-8). I wonder if there is some link between these two outputs. Like different units?

    The second picture shows that when I try to use the function “setParticlePosition” or “setParticleVelocity”, it always tell me error is “le id” even though I can ensure the id is correct. I used different type when I tried to debug, like int, double and others but found useless.

    What is wrong?

    Thank you again! I hope these pictures can help you identify why.

    Regards,

    Viki

    figure1.png figure2.png