-
Notifications
You must be signed in to change notification settings - Fork 447
Provide reference files for WES for ASCAT #100
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
Comments
Hi, |
So this issue is halfway addressed (see #606 ). It is possible now to use ASCAT with WES, however, we are currently not providing the necessary reference files: Reanme: Provide ASCAT WES reference files for GATK.GRCh38 |
Will move this to backlog, we can provide the references in 3.1 |
On a good way with this new beautiful documentation #981 |
I am unsure whether it actually makes sense to provide these files. Do all manufucatures use the same coordinates in their kits? Otherwise I think we should rather aim for making the generation as straight forward as possible |
Hi, just wanted to follow up on this. Does Sarek currently allow ASCAT on WES only data? |
Do you mean when there is no matched normal? |
Indeed matched normal is needed, but it was possible to extract some
meaningful information from WES data some time ago. The trick was to get a
decent loci file, first give a try to
https://github.com/VanLoo-lab/ascat/tree/master/ReferenceFiles/WES
references.
Cheers:
Szilva
…On Wed, 31 Jul 2024 at 09:21, Friederike Hanssen ***@***.***> wrote:
Do you mean when there is no matched normal?
—
Reply to this email directly, view it on GitHub
<#100 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEF342DTHFJWYD3EBJUT6Q3ZPCF57AVCNFSM6AAAAABLXD562OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJZHA2DGMZZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, I have matched normal, and already ran Sarek with the -wes option turned on with the matched normal, I just want to know how much i can trust the output, there were some github issues mentioned above which implied that Sarek may or may not be providing the correct .bed reference. |
Providing you are using the default igenomes settings, I would not trust
the results, since it is too sparse for WGS. What I would do:
- get the BED file that was provided with the WES kit, showing the targeted
regions
- select SNPs that are specific to the ethnicity and are overlapping to the
BED file above - note, you do not need all the SNPs only the common ones
- generate a file in the ASCAT loci format from this resulting VCF file
The alignment should be to the whole genome still, not only to the WES
regions.
Szilva
…On Wed, 31 Jul 2024 at 18:58, alexanderchang1 ***@***.***> wrote:
Hi, I have matched normal, and already ran Sarek with the -wes option
turned on with the matched normal, I just want to know how much i can trust
the output, there were some github issues mentioned above which implied
that Sarek may or may not be providing the correct .bed reference.
—
Reply to this email directly, view it on GitHub
<#100 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEF342GY5IXAIUZ7MGRQDATZPEJTTAVCNFSM6AAAAABLXD562OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQHE3DIMBYGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
To add to @szilvajuhos answer: here some commands to help you construct the loci file for your kit |
Hi, thanks, I will give this a shot. |
Issue by @Anuragksingh, moved from SciLifeLab#763
Comments:
@maxulysse
@szilvajuhos
@dingxm
@szilvajuhos
The text was updated successfully, but these errors were encountered: