Hi Jeremias,

I'm one of the OMA developers. This problem is quite strange to me - it's likely to be a problem of the slurm configuration that is different than the once we've so far tested. I would like to understand the problem a bit better to improve slurm support for OMA standalone. There two things I suggest to do:

1. try to set NR_PROCESSES outside your launch script, so before you do the sbatch command, just export the NR_PROCESSES there.

2. if it still fails, could you check to what the following environment variables are set in the job. For that, just change the call to oma with the following lines in your script file:

   echo "NR_PROCESSES $NR_PROCESSES"

   echo "SLURM_ARRAY_JOB_ID $SLURM_ARRAY_JOB_ID"

   echo "SLURM_ARRAY_TASK_ID $SLURM_ARRAY_TASK_ID"

   echo "SLURM_ARRAY_TASK_MAX $SLURM_ARRAY_TASK_MAX"

Thanks already for reporting.

Best wishes Adrian

Hi Adrian,

Thanks for your reply.

1. exporting in the shell used to submit the job did not work. OMA still thinks it is running as a single process.

2. I did two runs one where I included the "export NR_PROCESSES=2" command in the script and one without.

with the export command:

Starting database conversion and checks...

ERROR: failed to parse anything

NR_PROCESSES 2

SLURM_ARRAY_JOB_ID 13799019

SLURM_ARRAY_TASK_ID 1

SLURM_ARRAY_TASK_MAX 2

without the export command it again works as a single process:

Starting database conversion and checks...

WARNING: not run as a job-array. Will assume it is a single process

[...]

Done!!

NR_PROCESSES

SLURM_ARRAY_JOB_ID 13799064

SLURM_ARRAY_TASK_ID 1

SLURM_ARRAY_TASK_MAX 2