(→GPU codes) |
|||
(6 intermediate revisions by one user not shown) | |||
Line 3: | Line 3: | ||
{| style="background-color:#edebe7;" cellpadding="20" | {| style="background-color:#edebe7;" cellpadding="20" | ||
| __TOC__ | | __TOC__ | ||
− | !align="right" | <embed src=" | + | !align="right" | <embed src="https://stream.manchester.ac.uk/player51.swf" width="280" height="240" allowscriptaccess="always" allowfullscreen="true" flashvars="height=240&width=280&file=48176660_lo.mp4&streamer=rtmp://flash.stream.manchester.ac.uk/media/mp4:&searchbar=false&autostart=true&image=http://wiki.manchester.ac.uk/sphysics/images/DamBreak2D_Frame93_QuadK_Symplectic_pressure_i_Frame_0001.png"> </embed> |
|} | |} | ||
Line 51: | Line 51: | ||
'''[http://www.dual.sphysics.org/ DualSPHysics (CPU/GPU)]''' | '''[http://www.dual.sphysics.org/ DualSPHysics (CPU/GPU)]''' | ||
− | '' | + | ''[http://www.dual.sphysics.org/ v3.0 released December 2013]'' |
− | ''First released May 2011 | + | |
+ | ''v2.0 released March 2012'' | ||
+ | |||
+ | ''v1.0 First released May 2011'' | ||
[http://dual.sphysics.org/ www.dual.sphysics.org] | [http://dual.sphysics.org/ www.dual.sphysics.org] | ||
Line 67: | Line 70: | ||
'''[http://www.ce.jhu.edu/dalrymple/GPU/ GPU-SPHysics]''' | '''[http://www.ce.jhu.edu/dalrymple/GPU/ GPU-SPHysics]''' | ||
− | == | + | == Shallow water equations (SWEs) code == |
− | '''[[ | + | '''[[SWE-SPHysics | SWE-SPHysics]]''' |
− | '' | + | ''Released March 2013'' |
+ | |||
+ | |||
+ | '''[[SWE-SPHYSICS_1D_Download_v1.0 | SWE-SPHYSICS_1D_v1.0 ]]''' March 2013 | ||
+ | |||
+ | '''[[SWE-SPHYSICS_2D_Download_v1.0 | SWE-SPHYSICS_2D_v1.0 ]]''' March 2013 | ||
+ | |||
+ | ''' Documentation of the shallow water equation (SWE) code: ''' | ||
+ | |||
+ | You will need a copy of Acrobat reader to view the userguide ([http://www.adobe.com/products/acrobat/readstep2.html click here]). | ||
+ | |||
+ | To see how to reference the software, see '''[[SPHYSICS Reference| How to reference SPHysics]]'''. | ||
+ | '''[[Media:SWE-SPHysics v1.0.00.pdf | SWE-SPHysics v1.0.00.pdf]]''' March 2013 | ||
Note: The code developers are not required to fix bugs or ensure the code works under every development environment. Every care and attention has been made to ensure that the code is as portable as possible. | Note: The code developers are not required to fix bugs or ensure the code works under every development environment. Every care and attention has been made to ensure that the code is as portable as possible. |
There are various versions of the SPHysics code that can be downloaded. You need to create an account to continue to the Download pages (for help please contact the webmaster - see Developers).
|
SPHYSICS_2D_v2.2.001 January 2011
SPHYSICS_3D_v2.2.001 January 2011
Both versions (see Code features) include visualization codes for use on Matlab and ParaView.
Documentation of the serial code:
You will need a copy of Acrobat reader to view the userguide (click here).
To see how to reference the guide, see How to reference SPHysics.
SPHysics_v2.2.000_GUIDE.pdf October 2010
For complex geometry generation in 3-D, refer to the new Blender_for_SPHysics_v2.2_GUIDE.pdf October 2010
Click here to download older versions of SPHysics.
Released Jan 2011
parallelSPHYSICS_2D_v2.0 January 2011
parallelSPHYSICS_3D_v2.0 January 2011
Documentation of the parallel code:
You will need a copy of Acrobat reader to view the userguide (click here).
To see how to reference the software, see How to reference SPHysics.
parallelSPHysics_v2.0_GUIDE.pdf January 2011
v2.0 released March 2012
v1.0 First released May 2011
Click here to download DualSPHysics code v2.0
Documentation of the CPU/GPU code:
To see how to reference the software, see How to reference SPHysics.
Released March 2013
SWE-SPHYSICS_1D_v1.0 March 2013
SWE-SPHYSICS_2D_v1.0 March 2013
Documentation of the shallow water equation (SWE) code:
You will need a copy of Acrobat reader to view the userguide (click here).
To see how to reference the software, see How to reference SPHysics.
SWE-SPHysics v1.0.00.pdf March 2013
Note: The code developers are not required to fix bugs or ensure the code works under every development environment. Every care and attention has been made to ensure that the code is as portable as possible.