Simulation stopps

edited February 2014 in Old versions
Dear all,
I try to simulate a moving tank in 2d.
After starting the simulation it stops with the error:

[Initialising simulation (0zb43098) 18-02-2014 10:14:33]
PART PartTime TotalSteps Steps Time/Seg Finish time
========= ============ ============ ======= ========= ===================
Exception (JSphGpuSingle::Interaction_Forces)
Text: Failed in reduction of viscdt. (CUDA error: unspecified launch failure).



*** Exception (JSphGpuSingle::Interaction_Forces)
Text: Failed in reduction of viscdt.

Do anybody know what the reason is. I also tried a 3D-case with the same result.

Last Nvidia-Driver is installed.

Thank you for your support.

Best regards,

Benjamin

Comments

  • I try to simulate this case too and get error.
    As one of developers say (Stephen Longshaw) :

    "Simply calculate a set of acceleration values equivalent to the motion
    you wish to impart, keep your boundaries static and include the
    acceleration data (you will only need 1 file) as per the example case
    provided with DualSPHysics 3.0."
  • Dear Benjamin,
    I am interested in this case.
    Send please your results if you will handle problem well.
    Best regards,
    Sergey
  • Hello, in order to diagnose the problem with this case it would be useful if you could send through the xml of the case causing the error.

    There's a possibility that you have uncovered a bug in dualsphysics 3, so it would be good to see. If you are able please send the case through to me at my listed email address.

    The advice i gave to Sergey and that he has reiterated above, is the advice i would give to anybody trying to simulate a moving tank, in fact the variable acceleration functionality was introduced originally to exactly solve this problem.

    Best regards.
  • What GPU card are you using??
  • Hi,
    sorry for delay.

    We are using a 650Ti

    Greetings,

    Benjamin
  • Email us to dualsphysics@gmail.com with your problem and we will help you

    Regards

    Alex
  • I also meet the same problem when I debugg this code. Who can tell me how to settle it?
Sign In or Register to comment.