TCGA CNV data 1p/19q codeletion (whole arm deletion)
2
0
Entering edit mode
12 months ago
kwanghoon ▴ 20

Hi, I'm trying to get 1p 19q codeletion data from TCGA-GBM,LGG data.

I got CNV data of GBM, LGG and sorted chr1,19 that segment_mean <= -0.3 using R. (https://docs.gdc.cancer.gov/Data/Bioinformatics_Pipelines/CNV_Pipeline/)

If 1p/19q codeletion is exist, diagnosis can be "Oligodendroglioma". Not just deletion, I should find whole arm deletion at chr 1p and chr 19q codeletion.

What should I do...

TCGA CNV codeletion GBM LGG • 734 views
ADD COMMENT
1
Entering edit mode

Hi, I encountered the same problem, I spent about one week working on it, but I still can not find a solution.

Could you please share how you finally download the IDH mutation status and 1p/19q codeletion status data of TCGA-GBM and TCGA-LGG datasets? Thanks a lot in advance!

ADD REPLY
1
Entering edit mode

Hi, I think that the solution is as follows: if the information is not available in the clinical data, then you will have to define IDH status yourself, and also detect the co-deletion. It seems that IDH status may be available in the work linked by gabriel.rosser (see below)

ADD REPLY
1
Entering edit mode

Hi Kevin, thanks a lot for your kind reply. I finally find a way to download the IDH mutation status and 1p/19q codeletion status of TCGA-GBM and TCGA-LGG datasets. I put it here for future researchers:

***Using the following R code**

library(TCGAbiolinks)

library(openxlsx)

lgg_subtype <- TCGAquery_subtype(tumor = "lgg")

write.xlsx(lgg_subtype, file = "lgg_subtype.xlsx")

gbm_subtype <- TCGAquery_subtype(tumor = "gbm")

write.xlsx(gbm_subtype, file = "gbm_subtype.xlsx")

See more details here: https://www.bioconductor.org/packages/release/bioc/vignettes/TCGAbiolinks/inst/doc/subtypes.html

ADD REPLY
1
Entering edit mode

Excellent work - thanks. So, this information must have been in PanCancerAtlas clinical information. Noted for future!

ADD REPLY
1
Entering edit mode
12 months ago

Hi, you implied that you have already obtained the data. So, please proceed with your analysis.

You will have to develop some code that identifies deletion of the entire chromosomal arms. You can create rules that define whether an arm is deleted or not.

By the way: within the LGG (Lower Grade Glioma) TCGA cohort are already-identified oligodendroglioma samples (n=191). Please search the associated clinical data for LGG. The file is the BCR Biotab file, nationwidechildrens.org_clinical_patient_lgg.txt, available at the GDC Data portal.

To clarify: Lower Grade Glioma (LGG) is already classified into

  • Astrocytoma
  • Oligodendroglioma
  • Oligoastrocytoma

I was analysing these samples just a few weeks ago.

Kevin

ADD COMMENT
0
Entering edit mode

Hi Kevin. Thank you for your nice reply.

I know there is classified dx, but I was trying to check 1p/19q whole arm codel in Oligodendroglioma which is classified into "NOS" or "Anaplastic".

Do you think I don't need to do this?

Thank you again!

ADD REPLY
0
Entering edit mode

it depends what is the ultimate aim of your analysis / project?

ADD REPLY
0
Entering edit mode

I'm trying to check specific gene expression level of brain tumors between GBM, LGG(Astrocytoma, Oligodendroglioma) and including IDH mutataion status.

ADD REPLY
0
Entering edit mode

Then I think that you need to proceed as planned. Regarding the chromosomal arm deletions, you can develop some rule for 'aggregating' the copy number from multiple CN segments using the data that you have already obtained. One thing, for example, is to 'bin' each 50 segments and check the frequency of those below -0.3, and then 'slide' this bin across each chromosome, moving by 5 segments each time. There are different ways to do it.

ADD REPLY
1
Entering edit mode
10 months ago

This analysis has been carried out previously by Ceccarreli et al.. Look at Table S1 in that publication (column W).

ADD COMMENT

Login before adding your answer.

Traffic: 2545 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6