I'm invoking plass in the typical form on our high-throughput computing (slurm/sbatch) array:
plass assembly <reads_R1.fq> <reads_R2.fq> <plass_assembly.faa> tmp
Running on a single node and referencing the node-specific /tmp directory works fine, but in our system not all nodes have the required large amount of tmp space necessary (as in #4 ). Directing plass to use a local tmp folder works fine and has a much larger space allotment.
However, when I take advantage of the parallelization of slurm to run multiple jobs at once, the tmp folder I specify looks like this:
Am i correct in envisioning issues with the symlinking approach here? It looks like the multiple tasks might get confused with the "current" symlink as they iterate along.
I'm invoking plass in the typical form on our high-throughput computing (slurm/sbatch) array:
Running on a single node and referencing the node-specific /tmp directory works fine, but in our system not all nodes have the required large amount of tmp space necessary (as in #4 ). Directing plass to use a local tmp folder works fine and has a much larger space allotment.
However, when I take advantage of the parallelization of slurm to run multiple jobs at once, the tmp folder I specify looks like this:
Am i correct in envisioning issues with the symlinking approach here? It looks like the multiple tasks might get confused with the "current" symlink as they iterate along.
Thoughts?
Thanks~