Resolved....
Done!
A project by DCS Computing and CFDEMresearch
This website uses cookies to ensure you get the best experience on our website. By continuing to browse the site you are agreeing to our use of cookies. This website uses cookies. By continuing to browse the site you are agreeing to our use of cookies. More info
Misterblobby | Wed, 07/08/2015 - 15:28
Check the tutorials_public folder
Hi,
You are going to make a huge mess of the src folder very quickly if you put simulation files there.
Best to set up an individual folder with post, restart and mesh subfolders and set the dump commands to dump into those. Keep your input file in the same folder, similar to how the examples in liggghts-public\examples\liggghts\tutorials_public
To run it from there, typical command from terminal (inside the project folder) would be: mpirun -np 4 liggghts < bin_flow_commands_input_script.txt
The mpirun -np 4 part is not essential, but will speed things up. The 4 is for the number of processor cores you want to use. There's a way to set it up so that it defaults to the desired number of processors as well.
Hope this helps.
richti83 | Thu, 07/09/2015 - 08:16
short note
To make liggghts known systemwide, it is necessary to make a symbolic link in system-executable-directory (normaly /usr/bin/)
cd /usr/bin/
sudo ln -s /path/to/liggghts/src/lmp_fedora liggghts
(change lmp_fedora to lmp_ubuntuVTK / lmp_ubuntuVTK6 when you used another machinefile to make liggghts !)
now when you type liggghts anywhere in your shell it should promt with the version information.
In this way you don't need to copy the inputskript to the folder where the ligggghts executable lives !