Git Product home page Git Product logo

Comments (4)

mschatz avatar mschatz commented on August 13, 2024

from genomescope.

sallycylau avatar sallycylau commented on August 13, 2024

Hi Mike

Thanks so much for the quick reply. Here is the genomescope link (http://genomescope.org/genomescope2.0/analysis.php?code=tC8i3MBprfe3k57Irbbz). .hist file was generated with meryl. Any tips for how to fit the model would be much appreciated. Thank you!

from genomescope.

mschatz avatar mschatz commented on August 13, 2024

from genomescope.

sallycylau avatar sallycylau commented on August 13, 2024

Hi Mike

Thanks for your tips and sorry for the late follow up. I had to drop this project for a while and am now catching back up!

In your supplied link... I think setting "Average k-mer coverage for polyploid genome" to 40x which resulted in 3% het and 1.3 GB genome actually makes some sense....

I went ahead and assembled the genome with pretty aggressive purging (hifiasm -l3 + purged_dup) as this was found to give me the best completed assemblies (judging by N50 and contig #, and Complete BUSCO didn't vary much by changing hifiasm -l. Purged_dups definitely needed for duplications). I ended with a primary assembly of 1.8GB with BUSCO eukaryota C:96.90 [S: 91.80, D:5.10], F:1.2, M:1.9; and an alternate assembly of 1.3GB.

I ran Kraken on the purged assembles and 98.89% came back unclassified for primary and 99.97% for alternate, so I think contamination isn't the main issue here? We definitely only sequenced a single individual. This is a wild Antarctic brittle star from a place that receives a lot of current and gene flow from other places.... not ideal I am aware!

I ran smudgeplot as well and it does show this species as a diploid (but very heterozygous)

smudgeplot_smudgeplot

I tried to run Genomescope again with "Average k-mer coverage for polyploid genome" set as 30x which the estimated genome size came back as 1.9GB which matches the value in my purged primary assembly. However the fit is still quite poor. http://genomescope.org/genomescope2.0/analysis.php?code=PAA93V8MApgPGmKlPZrh

I wonder if there is still any way I could improve my Genomescope results? Thank you!

Best regards
Sally

from genomescope.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.