Skip to content

Conversation

@AustinHartman
Copy link

This doesn't take all the long to compute, and can be useful information to know. Also, databases like GenBank require read depth/coverage when assemblies are submitted.

graph.save_to_fasta(final_assembly_fasta, min_length=args.min_fasta_length)

# Align reads to assembly.fasta and report depth
get_read_depth(final_assembly_fasta, args)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to the reliance on assembly.fasta, read depth is calculated at the very end of the pipeline. Thus, the log header "Calculating read depth" and the depth information comes after the "Assembly complete" header. Maybe this behavior should be modified.

@AustinHartman
Copy link
Author

Depth in the log will appear as
When long reads and short reads are available:

Calculating read depth (2020-07-30 20:36:55)
--------------------------------------------
Short read depth:   54.48
Long read depth:    22.88
Total read depth:   77.36

When only one type (long or short reads) are available:

Calculating read depth (2020-07-30 20:36:55)
--------------------------------------------
Short read depth:   54.48

Base automatically changed from master to main March 15, 2021 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant