Closed greenprotist closed 3 months ago
This is the expected behaviour. pyabpoa
is required only for some niche functionality hence the warnings. The fact that your output ends with
Polished assembly written to medaka_telo_run2b/consensus.fasta, have a nice day.
suggests to me everything ran normally.
Hi, I have been running medaka on a Flye assembled eukaryote genome assembly (~200Mbp) with base-called nanopore reads (~17Gbp). The following is the command line used:
medaka_consensus -d /path/to/the/flye/assembly/fasta/file -I /path/to/base/called/nano/pore/reads -o medaka_out -m r941_min_fast_g303 -t 2
The run made it to the finish line, creating consensus.fasta among other files. The original and corrected files however look the same (just sequence order re-arranged), so I wonder whether or not medaka made any corrections.
This is how the first lines of the log file looks like (flagging that pyabpoa cannot be imported):
The followings are the ending lines:
My question is: was this run successful despite not being able to import pyabpoa? I've tried to install pyabpoa on the remote server computer but so far without success. If this medaka_consensus run doesn't require pyabpoa, assume I could proceed with the output consensus.fasta? I'd appreciate your comment. Many thanks. Happy New Year!