The subject spells out the root of the problem.
When PTP (on generic slurm) prepares a run configuration, it puts the
related batch file in $HOME/.eclipsesettings directory.
If the aforementioned directory is not on the compute nodes, then the launch will fail
with an error ---- "sbatch Exited with value: 1, sbatch err: Unable to open file .eclipsesettings/ccc....managed_file_for_script ..... job submit failed"
Changing the value of the environment variable HOME in the ".bashrc" or in the ptp configuration information dialog used to configure remote module loading will not change the outcome (the code may be using "getent passwd" which will ignore $HOME settings).
The "home" directory is used to specify ptpDirectory and other directories and files which may not exist on the compute nodes.
This means in particular, on large numbers of compute clusters and HPCs ( I have never worked on one in which "home" directories are mounted ) the Eclipse/PTP project is horrible broken "out of the box".
Is there some fix that will work in this case (home directory never mounted on compute nodes) ?
