TLD: AQUAgpusph vs. Experiments

Lets simulate the water case of the SPHERIC validation test number 9:

http://canal.etsin.upm.es/aquagpusph/gallery/picture.php?/11/category/4
http://canal.etsin.upm.es/aquagpusph/gallery/picture.php?/9/category/1

SPHERIC-2014

We go to the 9th SPHERIC workshop with IDOM as part of the SILER project.

More news coming soon!

Pressure sensors standard deviation

One of the main target of AQUAgpusph is the possibility to compute confident enough pressure values.

In this line the standard deviation of the interpolation process has been implemented in AQUAgpusph. Hence now you have a mean value, and a measurement of the dispersion of the data near to the sensor.

It could be extremely useful to get high quality pressure records:

Pressure record for the SPHERIC validation test number 10

In the previous figure the pressure computed in a simulation of the validation test number 10 of the SPHERIC benchmark is compared with the experimental results.

This new feature can be found in the unstable 1.5 branch of the code.

Performance improvements

As I reported some weeks ago, I’m working in the code optimization. To do it I implemented the following changes:

1. Now all the data (including the output one) is sorted before compute the interactions
2. Hence the permutations vectors are not needed anymore in the interactions stage
3. Some useless output data have been removed
4. The registers pressure have been optimized

Let’s say goodbye to more than 10% of the simulation time!

For the moment the optimized version can be found in the optimization branch of the git repository.
—
P.S. I performed this work with CodeXL by AMD, basically due to NVidia suddenly decided to remove the OpenCL support in the profiler in CUDA 5.
NVidia is expending a lot of resources trying to destroy OpenCL, while AMD is beating them in the hardware side (the real world).
I just hope NVidia people change it’s direction before they reach the final which are deserving.

Also CodeXL is free!

Rates kernel bottleneck

With the last changes implemented in the code the registries pressure during the interactions computations has been dramatically increased, which reduces the computation device occupancy.

This performance lost is my next target to fix (partially at least)…

The new Input/Output interface is released!

As it was announced here, the new Input/Output interface has been merged into the master branch, and it is ready to work.

In an user point of view several advantages could be considered:

• More intuitive XML input.
• XML backup saved in all the printed frame (so the simulation can be continued).
• Per fluid output files.

But the main benefits are for the developers due to now several base classes may be used and new readers/writers could be easily registered.

Anyway some work must be done, like moving the reports stuff which still be inside the server.

 

New input/output interface

A new input/output interface is coming… Following it’s features:

1. An easy way to implement new loaders/savers
2. Improved XML input
3. Capability to save the XML case definition (which allows to continue the simulation from the last saved file)
4. H5Part cleared
5. Improved the post-processing with Paraview (including tools to fix the errors with the locale options)

Actually it is in development in the input_output branch, but hopefully it will be merged soon