-
Notifications
You must be signed in to change notification settings - Fork 404
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
WES files provided by ascat author #1526
Comments
Hi! By default we supply the WGS files, but you should be able to fetch the files you want and supply them easily via the command line. THank you for flagging the updated files that are available, we can reflect this in our docs as well and link to it. |
looking forward to the update! I'm following this documentation and in point 3 I think I've encountered a typo in the 'awk' command right after 'do':
n=
I could only get the for loop to run when I used the line I've commented out instead that contains "chr". Is this expected behaviour? I'm using hg19 references Many thanks! |
Description of the bug
Hi Developers,
I'm trying to run the Sarek implemented ASCAT for CNV analysis on WES data. On the nfcore Sarek website, it's suggested to follow 5 steps, as specified in this doc https://nf-co.re/sarek/3.4.0/docs/usage#how-to-generate-ascat-resources-for-exome-or-targeted-sequencing, to generate reference information (allele.zip, loci.zip, GC.zip, and RT.zip) for exome data instead of using the default igenome directly. I noticed that the ASCAT author had also provided ref files for WES at https://github.com/VanLoo-lab/ascat/tree/master/ReferenceFiles/WES, which seemed to be a ready-to-use version when provided with an appropriate BED file. Would it be feasible to replace the default ignome ref with those for Sarek ASCAT?
I'm now running Sarek with params (-- --ascat_alleles, --ascat_loci, --ascat_loci_gc, --ascat_loci_rt) on the command line. The pipeline seems to work well. But, it would be great to hear advice from you.
Thank you!
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: