Skip to content

Simulation "explodes" just by changing the size of the tank #179

@ItsIronOxide

Description

@ItsIronOxide

Hi, I'm a master's student trying to use the SPlisHSPlasH open source code for my master's thesis. I am starting with a simple 3D dam break example similar to the one in this video.

What I don't understand is why changing the length of the tank, to allow the water to flow further without hitting the opposite wall, would cause the simulation to "explode" with particles going crazy. After reading a lot in the literature about SPH and its boundary handling methods, I still haven't figured out why this happens.

Below are three scene files I used to generate this simulation. You'll find that the files are identical, except the length of the tank (in the scale field of RigidBodies). The simulation runs smoothly for a tank length of 0.84 m, explodes for 3.6 m, but works just fine again for 4 m.

I'd really appreciate some feedback about why this weird behaviour is happening, as I've been trying to find some answers for months now.

dam_break_tank_length.zip

(Note: If some of the values in the scene JSON files seem awkward, that's because I'm generating them automatically with a python code I wrote, not writing them by hand. That's besides the point because the question here is: why does the simulation explode for specific tank sizes?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions