-
Notifications
You must be signed in to change notification settings - Fork 12
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
Queries on applying ONCOCNV on Exome Seq Data #14
Comments
Dear Vyomesh, Otherwise, it looks good to me. |
Hi Valentina Boeva, We are currently using ControlFREEC method & reproduce the same results in ONCOCNV. But we are finding difference in outcome. Test Sample (Output from ControlFEEEC): Test Sample (Output from ONCOCNV): Can you help in understanding why there is difference? Thanks, |
Dear Vyomesh, do you have .png images with the output of FREEC and ONCOCNV for this gene? |
I am lost.. I thought you had WES data.. But then why do you have so few regions in the OncoCNV output figure? |
For FREEC, you can generate the .png using an R script in the scripts folder |
Yes working on WES but have restricted gene list to approx. 1200 gene. Will try the R script for FREEC tool and share the details |
Hello Sir/Ma'am,
1] Trying to apply oncocnv for exome data i.e. without reference to amplicon id. What should be modification required in bed file for applying it on Exome data.
Standard bed file:
track name="4477685_CCP_Designed" description="Amplicon_Insert_4477685_CCP" type=bedDetail
chr1 2488068 2488201 AMPL242431688 0 TNFRSF14
Bed file used for Exome data:
track name="Covered" description="Illumina Exon - Genomic regions covered by probes" db=hg19
chr1 14694 14814 AMPL1354 0 WASH7P
Above bed file used, contains random amplicon id in 3rd column and 0 in 5th column, is it right strategy to use for Exon seq data?
2] While applying ONCOCNV for EXON data what precautions or prerequisite should be taken care of?
Kindly Guide.
Regards,
Vyomesh
The text was updated successfully, but these errors were encountered: