Protocol Overview / Introduction

In this protocol we discuss and outline the process of de novo assembly for small to medium sized genomes.

https://www.melbournebioinformatics.org.au/tutorials/tutorials/assembly/assembly-protocol/

Address of the bookmark: https://www.melbournebioinformatics.org.au/tutorials/tutorials/assembly/assembly-protocol/

More at https://ucdavis-bioinformatics-training.github.io/

Address of the bookmark: https://ucdavis-bioinformatics-training.github.io/2020-Genome_Assembly_Workshop/snakemake/snakemake_intro

Effective July 10, 2023, NCBI’s Assembly and Genome record pages now redirect to new NCBI Datasets pages. As previously announced, these updates are part of our ongoing effort to modernize and improve your user experience. NCBI Datasets is a new resource that makes it easier to find and download genome data.   

The following pages have been updated:

• The NCBI Assembly record pages now redirect to the new NCBI Datasets Genome record pages that describe assembled genomes and provide links to related NCBI tools such as Genome Data Viewer and BLAST.  
• The NCBI Genome record pages now redirect to the NCBI Datasets Taxonomy record pages that provide a taxonomy-focused portal to genes, genomes, and additional NCBI resources.   

During this transition, you will have the option to return to the legacy Genome and Assembly record pages. We will remove the legacy pages in early 2024.  

What is Genome Assembly?

Genome assembly involves piecing together short DNA sequence reads generated by sequencing platforms (e.g., Illumina, PacBio, Oxford Nanopore) into longer, contiguous sequences called contigs. This can be performed as:

• De Novo Assembly: Without a reference genome.
• Reference-Guided Assembly: Using a reference genome to guide the assembly process.

Step 1: Preparing Your Data

Before starting the assembly, ensure that your raw sequencing data is high quality.

1. Input Data

   • Short Reads: Illumina sequencing generates short, accurate reads ideal for scaffolding.
   • Long Reads: PacBio and Nanopore sequencing provide long reads for resolving repetitive regions.

2. Quality Control (QC)
   Use tools like FastQC or MultiQC to assess the quality of your reads:

   fastqc reads.fastq multiqc .

   Look for issues like low-quality bases, adapter contamination, or overrepresented sequences.

3. Read Trimming and Filtering
   Trim low-quality bases and adapters using Trimmomatic or Cutadapt:

   trimmomatic PE reads_R1.fastq reads_R2.fastq trimmed_R1.fastq trimmed_R2.fastq \ ILLUMINACLIP:adapters.fa:2:30:10 LEADING:3 TRAILING:3 SLIDINGWINDOW:4:20 MINLEN:36

Step 2: Choosing an Assembly Strategy

Select an assembly strategy based on your data type:

• Short-Read Assemblers:

  • SPAdes: Popular for microbial genomes.
  • Velvet: Fast for smaller genomes.

• Long-Read Assemblers:

  • Canu: Ideal for long-read datasets.
  • Flye: Versatile for small and large genomes.

• Hybrid Assemblers:

  • MaSuRCA: Combines short and long reads.
  • Unicycler: Optimized for bacterial genomes.

Step 3: Running the Assembly

3.1. SPAdes (Short-Read Assembly)

SPAdes is an excellent choice for small genomes, such as bacteria.

The output includes assembled contigs (contigs.fasta) and scaffolds (scaffolds.fasta).

3.2. Canu (Long-Read Assembly)

Canu is designed for high-error long reads from PacBio or Nanopore.

The output will be in canu_output/genome.contigs.fasta.

3.3. Hybrid Assembly with Unicycler

Unicycler combines short and long reads for improved assemblies.

Step 4: Assessing Assembly Quality

After assembly, evaluate its quality using the following tools:

1. QUAST
   QUAST generates assembly statistics, such as N50, genome size, and GC content:

   quast contigs.fasta -o quast_output

2. BUSCO
   BUSCO checks genome completeness by identifying conserved genes:

   busco -i contigs.fasta -o busco_output -l fungi_odb10 -m genome

3. Assembly Graph Visualization
   Visualize assembly graphs with Bandage:

   Bandage load assembly_graph.gfa

Step 5: Post-Assembly Steps

1. Polishing
   Improve assembly accuracy using tools like Pilon (for short reads) or Racon (for long reads).

   racon long_reads.fasta mapped_reads.sam contigs.fasta > polished_contigs.fasta

2. Scaffolding
   Link contigs into scaffolds using tools like SSPACE or Opera-LG if required.

3. Annotation
   Annotate the assembled genome using Prokka for prokaryotes or Maker for eukaryotes.

   prokka --outdir annotation_output --prefix genome contigs.fasta

Step 6: Sharing and Archiving

1. Submit to Public Repositories
   Share your assembly in databases like NCBI GenBank, ENA, or DDBJ.

2. Metadata Preparation
   Include detailed metadata for your submission, such as organism name, sequencing platform, and coverage.

Best Practices

• Always perform quality checks at each stage to ensure data integrity.
• Use multiple tools to cross-validate results when working with complex genomes.
• Document parameters and software versions for reproducibility.

Conclusion

Genome assembly is a powerful process that transforms raw sequencing data into a coherent representation of an organism’s genome. By following this step-by-step guide, you can successfully assemble genomes and uncover valuable biological insights. Whether you’re assembling a microbial genome or tackling the complexities of a eukaryotic genome, these tools and strategies will set you on the path to success.

mScaffolder scaffolds a genome using an existing high quality genome as the reference. It aligns the two genomes using nucmer utility from MUMmer and then orders and orients the contigs of the candidate genome guided by their alignments to the reference genome. Please send your questions and comments to mchakrab@uci.edu.

Citation https://www.nature.com/articles/s41588-017-0010-y

Address of the bookmark: https://github.com/mahulchak/mscaffolder

Address of the bookmark: https://github.com/CMU-SAFARI/AirLift

Genome Workbench can display sequence data in many ways, including graphical sequence views, various alignment views, phylogenetic tree views, and tabular views of data. It can also align your private data to data in public databases, display your data in the context of public data, and retrieve BLAST results.

Genome Workbench is built on the NCBI C++ ToolKit and uses cross-platform APIs for graphics. It runs on your local machine, and is available for Windows 2000/XP, Linux, MacOS X, and various flavors of Unix.

NCBI Genome Workbench is an integrated application for viewing and analyzing sequence data. Genome Workbench was developed entirely in-house at NCBI and makes use of the NCBI C++ ToolKit. The C++ ToolKit provides a convenient and flexible cross-platform API for managing system internals, database connections, network sockets, and the NCBI data model. In addition, the C++ ToolKit provides the Object Manager, which abstracts handling of sequences and sequence-related objects.

 New Features in Genome Workbench 2.7.15

• Multiple Alignment View: implemented adaptive feature display when zooming in
• Active Objects Inspector replaces Selection Inspector. New View should offer an improved selection context examination. See Using Active Objects Inspector tutorial for more details.
• Binary packages for Linux OpenSUSE 13.1 are now available

Bug Fixes and Improvements in Genome Workbench 2.7.15

• Fixed major issue with OpenGL overlay/scrolling. Could cause crashes or view scrolling irregularities
• Multiple Pane View: fixed crash on loading BLAST results
• Graphical Sequence View: fixed crash on zooming in and out, related to SNP track
• Graphical Sequence View: fixed Go To Position dialog to give better diagnostics in case of a user error
• Graphical Sequence View: PDF export fixed rendering of Markers with commas in the name
• Text View / Flat File: fixed Mac OS rendering issues
• Text View / Flat File: performance optimization, extended capabilities of real-time rendering of molecules to tens of thousands
• File Import: optimization improvement to speed up load of files containing multiple project items
• File Import: remapping stage now shows accession.version and description of molecules, instead of plain GI numbers
• Mac OS: improved tooltips for toolbar buttons
• Phylogenetic Tree Builder Tool: improved diagnostics of errors
• Multiple Alignment View: optimizations to avoid main GUI freezes
• Open Dialog: removed duplicate elements in table of genomes (load Genome)
• PDF export: fixed issue with XREF table errors
• Tree View: fixed issues with showing Force Layout progress on Mac OS
• Tree View: PDF export fixed issues for showing labels of collapsed nodes
• Tree View: added an option to stop layout
• Tree View: broadcasting mechanism fixed not to accumulate selected nodes

Reference:

NCBI news

http://www.ncbi.nlm.nih.gov/tools/gbench/

http://www.eva.mpg.de/genetics/bioinformatics/overview.html?Fsize=0%2C%20%40%2F%27

Kelso Group
Department of Evolutionary Genetics
Max Planck Institute for Evolutionary Anthropology
Deutscher Platz 6
04103 Leipzig
Germany
Phone: +49 341 3550 500

Job:
http://www.eva.mpg.de/genetics/bioinformatics/jobs.html?Fsize=0%2C%2B%40

Tasks:  239 total,   1 running,  238 sleeping,   0 stopped,   0 zombie

This line tells you how many processes are running. If you are using laptops machines it’s not so interesting because you really are the only one using this machine.

Cpu(s):  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

This line contains the CPU load. The first two numbers are how busy the system is doing computation (“us” stands for “user”) and how busy the system is doing system-y things like accessing disks or network (“sy” stands for “system”). We’ll talk more about this later.

Mem:   49457320k total,    3492174k used,  14535596k free,    1435148k buffers

This should be easy to understand – how much memory you’re using!

Swap:   539356k total,   28332k used,   836562k free,    29862014k cached

Swap is just on-disk memory that can be used to “swap” out programs from main memory. Again, we’ll talk about this later.:

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  1 root      39   19  0  0  0 S  0.0  0.0   246:57.22 kipmi0
  2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0

And... finally! What’s actually running! The two most important numbers are the %CPU and %MEM towards the right, as well as the COMMAND. This tells you how compute- and memory-intensive your program is. Right now, nothing’s running so the numbers aren’t very interesting, but just wait until we run something...