-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ww-poreCoV extension #275
Comments
Another interesting method might be VirPool: https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-022-05100-3 They illustrated already the advantage that longer amplicons bring w/ their method in particular.
They also tested the method on real data by sequencing a mixture of eight clinical samples using long amplicons (2kb). (sidenote, attention was brought up and information was shared by Victor! thx!) The question is, as usually, how up-to-date is the tool? https://github.com/fmfi-compbio/virpool They also provide scripts to create own profiles: https://github.com/fmfi-compbio/virpool?tab=readme-ov-file#creating-a-custom-variant-profile Maybe |
Yep, it's completely fine to extend Porecov now on the wastewater surveillance. We just need to make sure the normal "user experience" is not convoluted. |
ad You would use the VCF + BAM form ARTIC, right? Just to keep in mind: mixed indels might be tricky. edit: corrected tool name; Florida would be also a fun name |
Yes, I would like to use the output porecov anyway produces to change as little as possible. However, good point. I would live with such issues for now. Deconvoluting lineages from wastewater is anyway wild west :) but of course, important to keep such situations in mind. Ps: |
Not sure if it is possible to implement a subcommand or a second "main.nf" solely for the wastewater part? (thinking samtools subcommand for instance) |
I think subcommands are rather unusual - afaik, this is mainly handled by a parameter. Also, it could make trouble with the execution from GitHub |
Started working on this in a branch
|
The authors of However, we need to see if that works w/ nextflow |
This might be even more interesting to add as a process to ww-poreCov:
One big questions is probably: how do they handle the reference used for lineage assignments at the end? And: can they detect something new/cryptic |
Looking into
This might be a good option to build an up-to-date reference based on "representative spike sequences" per lineage (https://github.com/rki-mf1/sc2-mutation-frequency-calculator) |
re-tagged the provided image to |
Unfortunately, the container is a pain to use in Nextflow. Here is the Dockerfile and how then the tool is executed (a bash script): https://github.com/garcia-nacho/HERCULES/blob/master/Dockerfile#L76C19-L76C57 Probably, we need first to re-build the container. I tried to just |
garcia-nacho/HERCULES#2 (comment)
Hm okay.. similar issue like with CONCOMPRA |
Is this maybe interesting for our purpose of detecting smt new? https://github.com/zhuangx15/ICAvar |
Another idea: devider; https://www.biorxiv.org/content/10.1101/2024.11.05.621838v1 |
Another package from colleagues in France (Hughes has contact) where they reimplemented ww tools and making them faster Also
|
Virpool might be promising...
And the tool in the post before has a faster reimplementation of virpool |
Thomas is testing: https://github.com/bluenote-1577/devider |
That looks also promising, VILOCA: |
I suggest using the poreCov pipeline as the backend for SARS-CoV-2 wastewater lineage deconvolution from nanopore long reads. You already added
freyja
( #274 #270), which is great as the current community standard.However, we are also interested in detecting new stuff, aka "cryptic lineages" or novel mutation profiles.
To do this, I would like to test/implement two recent approaches:
CONCOMPRA
Floria
By this, we would get known lineage abundances from
freyja
plus potential new lineages from one or both of the other tools.Finally, we could also write a little ww-poreCoV extension paper ;)
The text was updated successfully, but these errors were encountered: