Step 4: Implement Kelager's suggested algorithm

As no progress was made using Unity's Rigidbody system, we decided to implement Kelager's algorithm fully. Most of the algorithm was already in place, as we used it to calculate forces when using the rigidbodies. What we needed to implement was the LeagFrog algorithm to calculate the next position and next velocity of each water particle and correct these using collision detection and management. In the video below the a first iteration of the algorithm can be seen. In the beginning the spheres fall in a promising manner, however they are quickly misplaced.



In the following pictures, as a video could not be recorded, the results of a second interation of the algorithm can be seen. Notice how the water does move and stay inside the boundaries, however the forces do not seem to be acting on the particles correctly. The velocities seem to be too high, which could either be a result from miscalculating the velocities themselves or from incorrect internal forces. Observe that what the pictures show are three frames right after each other - no fluid motion, only large changes in position.




Our next step is to try to figure out why these miscalculations occur and to find out if any other Kernel-functions can be used, other than the ones suggested by Kelager. We suspect that Kelager's suggested kernels might result in values that imply to large differences in positions in Unity's framwork at the scale we are using.

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

Step 2: Implementing the forces with Rigidbody

Bild
As it was time to implement the mathematics controlling the behaviour of the spheres, we quickly noticed that the pouring technique was not going to cut it. Taking a lot of inspiration for our math from Micky Kelager's paper Lagrangian Fluid Dynamics Using Smoothed Particle Hydrodynamics (2006), we realized that the number of available particles had to be a fixed number from the beginning of the simulation. Hence the obstacles and the pouring was removed and instead 200  - 400 spheres were placed at the scene in Unity. The scene in its current state can be seen in the figure below. Observe that we decided to not render the meshes of the cube to more easily see how the spheres behave, however they are still there. Following Micky Kelager's paper we implemented external forces in the form of gravity and surface tension and internal forces in the form of the viscosity force and pressure force, as well as all the surrounding math these forces required to work. We decided that ...
Läs mer

Step 6: Implementing the iWave algorithm

Bild
Further researching the iWave algorithm has shown us that this seems like a realistic approach. Due to the provided code in the paper mentioned in the last post, we have been able to make large strides in implementing the algorithm. To make our project a bit different and not only try to implement the algorithm described in the paper, we also decided to go back to our original idea of having a tap pouring water and interacting with the mesh to create waves. For details about the algorithm we recommend you read the original paper by Tessendorf  mentioned in the last blog post, however we will explain some nice-to-know parts of the algorithm that we deemed important. The algorithm is primarily focused on being interactive (hence we chose to add the tap again) and fast. By combining functions that calculate the height of water surfaces calculating a waves motion and functions that conserve the water masses, it is possible to create realtively realistic looking waves/ripples in the w...
Läs mer