Closed Biomicrogen closed 8 years ago
Hi,
When you let metAMOS auto-set a k-mer it relies on KmerGenie which has some dependences metAMOS doesn't install (R and required packages). I think there is a bug in the code where if it cannot run kmergenie it will give the error you are seeing rather than defaulting to k=31. Can you check the ASSEMBLE.log for error messages? There should also be a command to run KmerGenie in COMMANDS.log.
Closing, inactivity.
Program has been working great than all of a sudden I am getting this? Can't figure out why. I've been running with a set of manually entered kmer values and now I'm trying to run this with an auto selected value (without entering a -k option). Is there something I need to reset?
Initial command:
sudo ./initPipeline -q -1 /media/biomicrogen/U-Store-2/Processed-Seq/MiSEQ-270-PE1.fastq -2 /media/biomicrogen/U-Store-2/Processed-Seq/MiSEQ-270-PE2.fastq -c /media/biomicrogen/UBDISK/biomicrogen/BP-Trinity.fasta -d /media/biomicrogen/UBDISK/biomicrogen/runs/270-Trin -i 300:700 -W iMetAMOS
Run Command: sudo ./runPipeline -d /media/biomicrogen/UBDISK/biomicrogen/runs/Raw-Trin -v -o 40 -p 8 -f Scaffold -n Classify
Oops, MetAMOS finished with errors! see text in red above for details. Traceback (most recent call last): File "./runPipeline", line 985, in
verbose = 1)
File "/media/biomicrogen/UBDISK/biomicrogen/metamos/Utilities/ruffus/task.py", line 2965, in pipeline_run
raise job_errors
RethrownJobError: