-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very slow fluid simulation #52
Comments
What do you mean with "long time"? |
And how long did it take to calculate this simulation? And on which processor? |
I think the simulation took a few hours on two Xeon processors. However, you cannot compare FLIP particles with SPH particles. SPH solves the Navier-Stokes equations on the particle discretization while FLIP solves it on a fixed grid and only uses the particles to transport the quantities. It is easy to simulate millions of FLIP particles even in real-time. Take a grid with just one cell and put all inside. However, this gives you no more details. So you should compare the number of cells with the number of SPH particles. That said SPlisHSPlasH is typically not that slow. Did you build the library in "Release" mode? Does it run in parallel. Can you give me some simulation times? |
Question: Why is the simulator so slow? On my system, I simulate 15,000 particles for a long time.
Using the FLIP Fluids simulator on my system, I can simulate millions of particles. But with the help of splish slpash it turns out to simulate tens of thousands of particles.
Maybe I'm not correctly specifying the simulation parameters?
Here are the parameters of my simulation:
And one more question:
How do you position your splishsplash simulator?
Does this simulator belong to the category of 3D graphics or to the category of scientific programs for calculations?
That is, is splishsplash the same fluid simulator like realflow, houdini, blender elbeem, blender mantaflow, blender flip fluids?
Or all the same, the goals of this simulator differ from those listed above?
The text was updated successfully, but these errors were encountered: