Closed tadKeys closed 6 years ago
I think I found the error - it's probably misuse of binning and profiling
tools:
"clark": "p" <-- here
"kaiju": "p"
Best, Stephan
Hi Stephan,
Very probably that's the cause, because the sample data should produce meaningful results. Keep it in mind that if some tool does not have results, meaning the reads didn't match anywhere in the db, such error will still occur. That will be fixed on the v1.2.2.
Best. Vitor
Hi Vitor,
just wanted to let you know that the run completed.
Thanks and looking forward to the updates, Stephan
Hi,
I tested metameta now with an example file, and it also fails at the metameta step:
*) test.yaml
Input files: clark (p) sample1/profiles/archaea_bacteria_201503/clark.profile.out /home/stephan/work/01_meta_meta_db/archaea_bacteria_201503/clark.dbprofile.out kaiju (p) sample1/profiles/archaea_bacteria_201503/kaiju.profile.out /home/stephan/work/01_meta_meta_db/archaea_bacteria_201503/kaiju.dbprofile.out Taxonomy: /home/stephan/work/01_meta_meta_db/taxonomy/names.dmp, /home/stephan/work/01_meta_meta_db/taxonomy/nodes.dmp, /home/stephan/work/01_meta_meta_db/taxonomy/merged.dmp Bins: 4 Cutoff: 0.0001 Mode: linear Ranks: species Output file (type): sample1/metametamerge/archaea_bacteria_201503/final.metametamerge.profile.out (bioboxes) Verbose: False Detailed: False
Parsing taxonomy (names, nodes, merged) ...
Reading database profiles ...
Reading profiles ...