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
When you provide an output folder path that already exists, the program checks whether it's ok to use this folder, asking for input Y/N. This doesn't work in a non-interactive environment, such as in a job queue on a cluster.
For now, the simple solution is not to create the output folder in advance. Better if you could automatically refuse to write to an existing folder unless an argument flag is set?
The text was updated successfully, but these errors were encountered:
I use the query mode with the script bigslice --query ~/data1/LUCY/done_antismash/mag_gbk/ /efs/lucy1 -t 8 --program_db_folder /home/ec2-user/miniconda3/bin/bigslice-models
but with the error "Output folder didn't exists! BiG-SLiCE run failed."
And I have tried not to create the output folder in advance, and create the output folder.
I always meet this error.
Could you offer any tips about this problem?
I use the query mode with the script bigslice --query ~/data1/LUCY/done_antismash/mag_gbk/ /efs/lucy1 -t 8 --program_db_folder /home/ec2-user/miniconda3/bin/bigslice-models
but with the error "Output folder didn't exists! BiG-SLiCE run failed."
And I have tried not to create the output folder in advance, and create the output folder.
I always meet this error.
Could you offer any tips about this problem?
When you provide an output folder path that already exists, the program checks whether it's ok to use this folder, asking for input Y/N. This doesn't work in a non-interactive environment, such as in a job queue on a cluster.
For now, the simple solution is not to create the output folder in advance. Better if you could automatically refuse to write to an existing folder unless an argument flag is set?
The text was updated successfully, but these errors were encountered: