-
Notifications
You must be signed in to change notification settings - Fork 28
Bad dataset analysis
Ryan Wick edited this page Jul 7, 2020
·
5 revisions
To begin, I ran Trycycler cluster on the assemblies:
trycycler cluster --reads reads.fastq.gz --assemblies assemblies/*.fasta --out_dir trycycler
Which produced this output.
A whopping 69 clusters were made, and the tree looks hideous:
There are no clear clusters here on which we can apply further stages of Trycycler 😢
This dataset was a bit of a trick – it's unusable rubbish. In a situation like this, it is necessary to back up to an earlier stage. Perhaps different assemblers or assembly parameters can make better input assemblies for Trycycler. Or it might be necessary to resequence the genome to get longer/deeper/better reads to assemble.
It's worth reiterating here: Trycycler is not a tool for coaxing a difficult read set into a decent assembly. Rather, it's a tool for taking a good read set and making a great assembly.
- Home
- Software requirements
- Installation
-
How to run Trycycler
- Quick start
- Step 1: Generating assemblies
- Step 2: Clustering contigs
- Step 3: Reconciling contigs
- Step 4: Multiple sequence alignment
- Step 5: Partitioning reads
- Step 6: Generating a consensus
- Step 7: Polishing after Trycycler
- Illustrated pipeline overview
- Demo datasets
- Implementation details
- FAQ and miscellaneous tips
- Other pages
- Guide to bacterial genome assembly (choose your own adventure)
- Accuracy vs depth