You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the mantis deskew CLI call processes positions consecutively. We can process positions in parallel using slurm by calling a python script: python slurm_deskew.py, after we modify the script with the right dataset parameters. It would be convenient to merge the two pipelines and add an optional --use_slurm flag to mantis deskew, e.g.
with optional parameters such as --cpus_per_task or --mem_per_cpu.
Based on our discussion this morning, processing datasets with slurm is not fool-proof enough to be abstracted as a CLI call. At this point calling a python script is the more appropriate format. We decided to revisit that after more experience with running parallel slurm jobs.
The text was updated successfully, but these errors were encountered:
After discussion, @edyoshikun and I agree that this is not on the immediate critical path. We're planning to continue using slurmkit scripts for our analyses.
Currently the
mantis deskew
CLI call processes positions consecutively. We can process positions in parallel using slurm by calling a python script:python slurm_deskew.py
, after we modify the script with the right dataset parameters. It would be convenient to merge the two pipelines and add an optional--use_slurm
flag tomantis deskew
, e.g.with optional parameters such as
--cpus_per_task
or--mem_per_cpu
.Based on our discussion this morning, processing datasets with slurm is not fool-proof enough to be abstracted as a CLI call. At this point calling a python script is the more appropriate format. We decided to revisit that after more experience with running parallel slurm jobs.
The text was updated successfully, but these errors were encountered: