-
Notifications
You must be signed in to change notification settings - Fork 55
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
How the calculated the decay line by nonlinear regression to the LD plot? #10
Comments
Dear @sekhwal By the way : A: Due to the relationship between the r2 of ld decay and the physical distance, when the Ref scaffols connected to LG, the order of the scaffols is wrong or the length of N inserted in the middle is seriously wrong, this is very likely to affect the result. Solution: In this case, you can return to the original scaffold coordinates and take the long scaffolds to analyze B: SNP of RAD or GBS sequencing or chip data may cause this situation . Solution: In this case, You can try to increase these three parameters [ -bin1 -break -bin2 ]when you draw, it will smooth your curve, like : |
the decay line fluctuation is Due to youre poor assembly ref ( Ref assembly quality is too poor ). a) PopLDdecay-3.41/bin/PopLDdecay -MaxDist 500 can make the physical distance to 500 kb Due to the relationship between the r2 of ld decay and the physical distance, when the Ref scaffols connected to LG, the order of the scaffols is wrong or the length of N inserted in the middle is seriously wrong, this is very likely to affect the result. Solution: In this case, you can return to the original scaffold coordinates and take the long scaffolds to analyze |
Hi, I am trying to add the non-linear regression tendency line to the Linkage Disequilibrium (LD) plot. I followed the manual document of PopLDdecay and got the plot. However, I am looking to make plot like above where r2 only goes until 0.5 and physical distance until 500 kb.
Got the plot using PopLDdecay.
However,
I am looking the LD plot like this with dots.
The text was updated successfully, but these errors were encountered: