Unable to run lmp_auto on a cluster

Submitted by AzamatSalamat on Tue, 04/28/2020 - 15:04

Hello, everyone!

I have installed LIGGGHTS on our university cluster (CentOS 7.4) with VTK turned off. The compilation was complete and lmp_auto file was created.
I have copied the lmp_auto file to the folder with chute_wear example to check how it is working. However, when I tried
mpirun -np 4 lmp_auto < in.chute_wear
the following error appeared:

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: cluster_name
Executable: lmp_auto

Note that I am an undergrad student and this is a university cluster so I don't have any root access. Therefore, I am not able to create any symbolic links as in this post https://www.cfdem.com/forums/how-run-input-script-given-tutorial.
I am just wondering why mpirun is not able to detect the executable when it is the same folder.

Best regards,
Azamat

AzamatSalamat | Tue, 04/28/2020 - 17:18

Just to note, since I do not need VTK, I had to run make auto first time to generate the Makefile.user file. I changed the USE_VTK to "OFF" in it and then had to run 'make clean-all' and 'make auto' again. So on the second try, LIGGGHTS was compiled successfully (seems so).

AzamatSalamat | Wed, 04/29/2020 - 11:31

In case if someone needs this,
So apparently, lmp_auto does not work from outside the src directory where it was originally created. No need to create any links or add to the path environment or anything else if you do not have root access.
Case files, in files, meshes etc. can be just copied to the src directory and the mpirun runs perfectly from there
The only thing left for me is an alternative for the VTK outputs...

tjleps | Sat, 05/02/2020 - 07:06

You definitely can run lmp_auto from a different directory then it was compiled, though you can also call the executable from a central location using: "mpirun -np 4 /path/to/lmp_auto < in.chute_wear" without having to link it.
It sounds like you may have copied the file incorrectly, or ended up in the wrong directory... Also check to make sure that any modules used at compile time are loaded in the terminal you're running from.

AzamatSalamat | Sun, 05/03/2020 - 07:52

Thanks, that works well too