Closed jolespin closed 5 years ago
Hello
This step is I/O-bound, so please double check that everything is ok here.
PS: The latest version of SPAdes is 3.13.0 and it contains some updates especially for rnaSPAdes.
This is good to know. I will request that we update to 3.13.0 on our servers. I ran rnaSPAdes for a similar dataset and it ran perfectly.
This step is I/O-bound, so please double check that everything is ok here.
Is there any file in particular I can check to make sure this is ok?
Thanks for getting back to me so quickly btw.
Is there any file in particular I can check to make sure this is ok?
Well, you may want to check in the system logs, you may want to check the process status via "top", etc.
I'm running on the grid:
qsub -cwd -P 0749 -pe threaded $N_JOBS -M jespinoz@jcvi.org -m e -N frozen_rnaspades "/usr/local/projdata/9043/projects/MGX/localenv/envs/spades/bin/rnaspades.py -s seq_raw/frozen_unmapped.fastq -o rnaspades_output/frozen/ -t $N_JOBS"
Here's my qstat:
job-ID prior name user state submit/start at queue jclass slots ja-task-ID
------------------------------------------------------------------------------------------------------------------------------------------------
9434455 0.56506 frozen_rna jespinoz r 02/28/2019 01:19:49 default.q@dell-2.jcvi.org 16
I'm not sure if top
captures those processes. Is there a way for me to kill the job via qdel 9434455
and resume using the files already created?
Well, then I would suggest you to ask your system administrator, how the things could be troubleshooted on the cluster.
Sadly, there is no way to restart from this stage.
Oh ok, thanks for the responses. I'll kill the job and try again with the newest version w/ a fresh conda env.
conda create --name spades_env -c bioconda spades
b/c it looks like the version is v3.13.0
https://anaconda.org/bioconda/spades
There seems to be conda version, yes, though we do not maintain it.
Here's my
spades.log file
:Let me know if there is any other information you need and I will update accordingly.