How about SLURM_ARRAY_MIN_TASK_ID, SLURM_ARRAY_MAX_TASK_ID and
SLURM_ARRAY_NUM_TASKS?
I agree with Kilian's reasoning. I think it's helpful to the end user
to follow a pattern consistent with the --ntasks variables.
FYI, SLURM_ARRAY_NUM_TASKS is the only one I would foresee myself using,
but the others should be easy enough to add while I'm in there...
In my most recent case, it's a matter of partitioning a FASTA file for
parallel BLAST+ searches.
Regards,
Jason
On 3/13/15 11:33 PM, Morris Jette wrote:
That depends what you want to see for
--array=1,100
The 100 or 2 or perhaps both?
Perhaps Slurm_array_max_task_Id and Slurm_array_task_count
On March 13, 2015 8:35:27 PM PDT, Kilian Cavalotti
<[email protected]> wrote:
On Fri, Mar 13, 2015 at 6:34 PM, Jason Bacon <[email protected]> wrote:
by creating a new variable such as SLURM_ARRAY_NUM_TASKS?
On Fri, Mar 13, 2015 at 7:17 PM, Moe Jette <[email protected]> wrote:
How about this for a name? SLURM_ARRAY_MAX_TASK_ID
I like SLURM_ARRAY_NUM_TASKS better, it's more like the existing variables.
Cheers,
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jason W. Bacon
[email protected]
If a problem can be solved,
there's no need to worry.
If it cannot be solved, then
worrying will do no good.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
