-
Notifications
You must be signed in to change notification settings - Fork 46
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
Problem in the deconvolution step #148
Comments
Hi, sorry for the slow answer, I only came back from vacation this week.
By the way, the wastewater specifics have now been merged into the main master branch.
Could you also provide the deconvoluted.out.log? This would provide details about the parameter users to deconvolute. (It recapitulates all what was loaded from the various .yaml files and/or autoguessed from the data).
Indeed that's the problematic part. For some reason it can't generate a deconvolution for the given input parameters.
Normally, the dates should be autoguessed from the range of the "date" column in results/tallymut.tsv.zst Could you also provide your V-pipe config file? Among other:
Regarding file var_dates.yaml: E.g.: if before 2022-07-1 you have a different mixture of variant, and it changes afterward, you just write: var_dates:
'2022-05-01':
# at the beginning of the project, only B.1.1.7 'Alpha', P.1 'Gamma' are present
- B.1.1.7
- P.1
'2022-07-01':
# starting from huly, Delta B.1.617.2 and Omicron BA.1 showed up to the party
- B.1.1.7
- B.1.617.2
- P.1
- BA.1 This will cause Lollipop to do one deconvolution for all samples between May and July while looking only for quantification of B.1.1.7 and P.1, The way you wrote you yaml, LolliPop will start one deconvolution each month (from 2022-06-12 to 2022-07-17, then 2022-07-17 to 2022-08-14, then 2022-08-14 to 2022-09-18, then everything after 2022-09-18) but you asked each time to estimate the proportion for the same mixture of variants (B.1.1.7, B.1.617.2, P.1, BA.1). |
Hi @DrYak , I run this time with only 2 variants (Alpha and Delta) from the references/voc this time. Here is the deconvoluted.out.log file
Here is my config.yaml file:
I let V-pipe reuse the results/variants_pangolin.yaml file.
The variants Alpha (B.1.1.7 ) and Delta (B.1.617.2) always appear, so I adjust the var_dates.yaml like this:
My regex.yaml file:
My wastewater_plants.tsv file:
After all that, it returned the same error as before :) |
Well I don't see anything anomalous... Could you share me the compressed tallymut.tsv.zstd over, e.g. PolyBox, Switch Drives, etc. so I could have I try to see what's wrong? |
Hi @DrYak
Here is the file over google drives: Thank you! |
Following the guide for wastewater experimental branch. I got stuck in the last stage of vpipe deconvolution as you can see in this error log: deconvoluted.err.log.
More specifically, the problem happens when running this code inside lollipop: (deconvolute.py)
will return an empty data frame. I noticed that in the generated variants_pangolin.yaml file start_date and end_date is not added in the previous step. Adding it manually does not solve the problem.
The content of the input files is as follows:
results/tallymut.tsv.zst contains:
I just printed out 10 out of 2096 rows of the above data frame in python.
deconv_bootstrap_cowwid.yaml:
results/variants_pangolin.yaml:
var_dates.yaml:
What can I change to make vpipe deconvolution work? Alternatively, what anaconda and jupiter notebook version do I need for the lollipop code to run?
The text was updated successfully, but these errors were encountered: