Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The difference between medaka inference and medaka_consensus in medaka version 2.0.1 #542

Closed
hungweichen0327 opened this issue Nov 18, 2024 · 1 comment
Labels

Comments

@hungweichen0327
Copy link

Dear community,

I would like to ask about the difference between medaka inference and medaka_consensus in medaka version 2.0.1.

Based on the manual below, the input read file of medaka inference is the bam file:

# align reads to assembly
mini_align -i basecalls.fasta -r assembly.fasta -P -m \
    -p calls_to_draft.bam -t <threads>
# run lots of jobs like this:
mkdir results
medaka inference calls_to_draft.bam results/contigs1-4.hdf \
    --region contig1 contig2 contig3 contig4

While in the medaka_consensus, the input read file of medaka inference is the fasta/fastq file:

NPROC=$(nproc)
BASECALLS=basecalls.fa
DRAFT=draft_assm/assm_final.fa
OUTDIR=medaka_consensus
medaka_consensus -i ${BASECALLS} -d ${DRAFT} -o ${OUTDIR} -t ${NPROC}

I was wondering, in addition to the input file format of the raw ONT reads, whether the final polished genome.fasta is the same or not.

Thank you for the help.

@hungweichen0327 hungweichen0327 changed the title The difference between The difference between medaka inference and medaka_consensus in medaka version 2.0.1 Nov 18, 2024
@cjw85
Copy link
Member

cjw85 commented Nov 18, 2024

medaka_consensus is a convenience bash script for running a workflow starting from a draft sequence and fastq files. It uses medaka inference internally in much the same way as the example in the README.

@cjw85 cjw85 closed this as completed Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants