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
I am using make_lastz_chains version 2.0.8 in our Slurm cluster. When I run the test example ./make_chains.py target query test_data/test_reference.fa test_data/test_query.fa --pd test_out -f --chaining_memory 16 --cluster_executor slurm --cluster_queue long, the pipeline terminates at the lastz step. In the nextflow.log from the temp_lastz_run directory an exit code 132 leading to the termination is documented.
However, when I run ./make_chains.py target query test_data/test_reference.fa test_data/test_query.fa --pd test_out -f --chaining_memory 16 from an sbatch script where the cluster_executor is local, the pipeline does not terminate.
I'd appreciate your thoughts on what might be causing this issue.
The text was updated successfully, but these errors were encountered:
Hi @kirilenkobm and @MichaelHiller,
Thank you for providing this pipeline!
I am using make_lastz_chains version 2.0.8 in our Slurm cluster. When I run the test example
./make_chains.py target query test_data/test_reference.fa test_data/test_query.fa --pd test_out -f --chaining_memory 16 --cluster_executor slurm --cluster_queue long
, the pipeline terminates at the lastz step. In the nextflow.log from the temp_lastz_run directory an exit code 132 leading to the termination is documented.However, when I run
./make_chains.py target query test_data/test_reference.fa test_data/test_query.fa --pd test_out -f --chaining_memory 16
from an sbatch script where the cluster_executor is local, the pipeline does not terminate.I'd appreciate your thoughts on what might be causing this issue.
The text was updated successfully, but these errors were encountered: