Conversation
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 772479a3db
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
please address the above two bugs |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 990f17ee20
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
I got this error from the great age dataset I think this is because no ancestral allele information is provided for the great ape data, so for multiple datasets, the |
|
I encountered this issue before. I wonder if adding So it only takes datasets in account that have |
|
We need to add |
|
also revise this: selscape/workflow/rules/common.smk Lines 76 to 80 in 9fa0059 with |
|
When one dataset doesn’t have |
|
Hi @xin-huang |
|
I do not have the bandwidth to investigate this issue in detail. However, I am not yet convinced that the |
|
pop.list samples While 1kg_low have over 100 samples for each population. greatape dataset has 10 PPA samples and 1kg_high has only 5 for each population. frequency spectrum greatape frequency spectrum 1kg_high frequency spectrum 1kg_low We can see that 1kg_low has more data within the fs comapred to greatape and 1kg_high. It should be enough to successfully ran the dadi analysi. When I used unfolded data it worked without problems. bootstraps greatape bootstraps 1kg_low bootstraps 1kg_high It only shows 0 for I compared I excluded So I guess there is something wrong with the current implementation of the ancestral allele gating. |
|
Good, the bootstrapping spectrum indicates the cause of this Also, the sample size is not correct in the 1kg_high_cov spectrum. So you should check if there is anything wrong when generating the spectrum. |
selscape/examples/get_1kg_high_cov.smk Lines 56 to 71 in 2a7f9ff I think |
|
However, the same settings worked previously in version 1.0.0, so the key question is why the bootstrapped spectrum is empty now. |
|
any update? |
|
It is clear that currently using unpolarized data, it leads to empty bootstrapping fs, while using polarized it SNPs exist in the bootstrapping fs. output: output The issue is, that I still do not know, where the root problem is. In the past days I was looking at the dadi-cli source code, hoping I can find any clues. selscape/workflow/envs/selscape-env.yaml Line 10 in 9fa0059 I suggest to update this version to - dadi-cli=0.9.14.
|
|
Because polarized ist always set to I also looked at the input files and This could explain why 1kg_low worked. Its processed VCF contains an AA field, so even with polarized=True, dadi could read the ancestral alles and generate non-empty bootstraps. greatape and 1kg_high do not have an AA field, so the forced polarized=True results in empty bootstraps. |
|
@xin-huang |
|
I will merge this one. Please continue adding the Circos plots. |
No description provided.