Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Summer 1, Summer 2, Summer 3, Summer 4
Description
GOAL: To try a preliminary test run of spades on a Kelsey dataset.
This is a simple pilot run.
From this we can learn some nuances of spades and do a new ticket to do an official run.
Rob will get the URC folks to make a module of the latest SPADES release from earlier this week.
Why Spades?
Trinity creates hundreds of thousands of contigs and is a messy difficult tool.
https://academic.oup.com/gigascience/article/8/9/giz100/5559527
"This article is from 2019, so it may be a little dated. It compared several de novo transcriptome assemblers, such as Trinity and Bloom. Something cool is that it calculates the k-mer size based on read length and it has a lower duplication ratio when compared to trinity or bloom." Brandon
Trinity has a massive duplication problem it seems.
Attachments
Activity
I have submitted a help ticket to the URC to have them make Spades a module.
That should solve the issue in the easiest manner for all!
SPAdes 4.0.0 is now installed and available for use on the HPC cluster.
2 Spades runs were completed successfully. Waiting on the other two. Collected numerical data is being collected in the two spreadsheets below, I will complete the sheets as soon as I have the outputs from Nag and Tam.
Output file results: https://docs.google.com/spreadsheets/d/1Jnxqw9v8HoOMqpJAu8kRFLAuIw0vuc2YIE7irzs7Tn8/edit?usp=sharing
Tam finally completed, and all contigs have been generated for each variety.
Installed Spades v4.0.0, it is located in /projects/tomato_genome/sw
I tried to run a test script, but Python on the cluster is version 3.6.8, and the new spades only work with Python versions 3.8 and up.