Skip to content
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

Msisensor on WES-T vs WGS-C #20

Open
Ephedria opened this issue Mar 9, 2021 · 1 comment
Open

Msisensor on WES-T vs WGS-C #20

Ephedria opened this issue Mar 9, 2021 · 1 comment

Comments

@Ephedria
Copy link

Ephedria commented Mar 9, 2021

Hello,

First, thank for your tool, it is really useful.

I was wondering if using different technology can include a bias.
To be more clear :
I have several samples which I analyze using the WGS-T against the WGS-C.
I also have the WES-T on these samples. I used the WES-T against the WGS-C.
The comparison on these samples show a lot of discrepancy : comparison using WES-T / WGS-C tend to show more Unstable status than the comparison WGS-T / WGS-C .

Since the coverage is different, ( ~200X for the WES-T and ~60X for the WGS-T) can it explain this bias ?

Best,

@owehann
Copy link
Contributor

owehann commented Mar 20, 2021

Hi Ephiedria
Sorry for the late feedback. It is not recommended for paired MSI calling using different types of sequences. Besides, there are more microsatellites in WGS, which leading to more valid sites (denominator of MSIscore). We do not think that coverage is the main point, and suggest that you can compare the difference in the number of valid sites and unstable sites obtained by your trails.
Thanks
Xinyin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants