Hi all,
I have got question about how to compile the 'in.filename' in parallel without copy executable 'lmp_auto' into the same folder. As suggested by the Liggghts documentation that the final step to make it compiled is
"cp lmp_auto ../examples/LIGGGHTS/Tutorials_public/chute_wear
cd ../examples/LIGGGHTS/Tutorials_public/chute_wear
mpirun -np 4 lmp_auto < in.chute_wear"
It can be compiled properly by using "liggghts < in.filename" with or without executable in the folder, also it works well by copying executable 'lmp_auto' to each folder, but failed when there is no 'lmp_auto' within the same folder as shown below
"mpirun was unable to find the specified executable file, and therefore
did not launch the job. This error was first reported for process
rank 0; it may have occurred for other processes as well.
NOTE: A common cause for this error is misspelling a mpirun command
line parameter option (remember that mpirun interprets the first
unrecognized command line token as the executable).
Node: DESKTOP-0000
Executable: lmp_auto"
However, is their anyway to compile any "in.filename" from any folder without copying 'lmp_auto' each time, please advice!
Many thanks!
Zen
mschramm | Wed, 10/16/2019 - 08:32
Symbolic links
Hello,
You do not compile in.liggghts files. They are simply text files to feed in commands to liggghts.
Once the executable lmp_auto is created a symbolic link is often used to place a callable link in a folder that is party of the PATH variable.
I use use/local/bin myself.
Now when I use the command liggghts, the link then calls the executable.
From your post, it seems you already have a link via liggghts. Did you make changes to the code and need to make a new link?
zen | Tue, 11/26/2019 - 15:33
sovled
Hi Mschramm, thanks for your comments, problem sovled.