News:ChIPpeakAnno::getAnnotation get Exons
2
0
Entering edit mode
Julie Zhu ★ 4.3k
@julie-zhu-3596
Last seen 13 months ago
United States

Dear Paola,

To get the exon annotation, please set featureType to "Exon" as follows.

x<-getAnnotation(mart, featureType= "Exon")

To find out more about this function, please type help(getAnnotation) in a R session. Thanks!

Best regards,

Julie


On 3/20/15 5:46 AM, "paola.orsini-@libero.it" <paola.orsini-@libero.it> wrote:

Dear doctor,
I'm Paola Orsini, I'm a biologist and bioinformatician from the university of Bari (Italy). I'm analyzing ChIP-seq data and I'm using your package ChipPeakanno to annotate my peaks.  I would like to kindly ask you some information about it. In details, in chippeakanno manual I read that you can annotate peaks using the annotatePeakInBatch function directly by using some annotation data packages (such as TSS.human.GRCh37) to annotate peaks with TSS, if we want to annotate them with other genomic features (such as exon, mirna or utr), we have to use getAnnotation function. I tried to annotate my peaks in both ways here the script I wrote:

data(TSS.human.GRCh37)
annotatedPeak1 = annotatePeakInBatch(peaks, AnnotationData=TSS.human.GRCh37)


listMarts()  
mart = useMart('ensembl',dataset="hsapiens_gene_ensembl")
x<-getAnnotation(mart,
featureType=c("TSS","miRNA", "Exon", "5utr", "3utr", "ExonPlusUtr", "transcript"))
class(x)    #RangedData
annotatedPeak2<-annotatePeakInBatch(peaks,AnnotationData=x)

I saw that the two annotation files are the same, in that the second file doesn't include the additional information I expected. I don't know if I'm making some errors, unfortunately I've not experience in this kind of analysis.

I also used the addGeneIDs function to add other IDs to annotated peaks, and I observed that for some ENSG Id, the associated  gene symbol and entrez ID are not in the output (most of them areNA), even if for some of them there is a gene symbol in Ensembl database (for example ENS0000023176).
I would also like to ask you if with the assignChromosomeRegion function we can retrieve which are the peaks associated with each region or only their percentage.
Thank you very much for your time and kind attention.
Best regards,

Paola

chippeakanno News • 1.8k views
ADD COMMENT
0
Entering edit mode
@paolaorsini-7506
Last seen 7.9 years ago
Italy

Hi Julie,

thank you very much for your reply! I would like to ask you another information  about the ChipPeakAnno annotation. In details, I firstly used TSS.human.GRCh37 data to annotate my peaks by using this code:

>annotatedPeak1 = annotatePeakInBatch(peaks,AnnotationData=TSS.human.GRCh37, output="both",multiple=T,maxgap=0)

  I also applied getAnnotation function with the following code to use hg19 version and to obtain TSS and mirna data:

>mart_hg19=useMart('ENSEMBL_MART_ENSEMBL',dataset='hsapiens_gene_ensembl',
>host="may2012.archive.ensembl.org")

>tss<-getAnnotation(mart_hg19,featureType="TSS")

>annot.tss<-annotatePeakInBatch(picchi2, mart_hg19, featureType ="TSS",output="both",multiple=T,maxgap=0)

When I applied addGeneID function to add common IDs such as gene symbol or entrez ID, I observed that the two annotations (annotatedPeak1 and annot.tss) obtained are not exactly the same for some peaks. I think the two solutions should both refer to the hg19 human release, I don't know in what they differ..

Could you give any suggestions about how this?

Thanks!

Best,

Paola

 

 

 

 

ADD COMMENT
0
Entering edit mode
Ou, Jianhong ★ 1.3k
@ou-jianhong-4539
Last seen 3 days ago
United States

Hi Paola,

The TSS.human.GRCh37 is generated at March 2010, which ensembl did not generate archive file for that. As you mentioned this annotation is very close to Aug2010. After that we did not update the annotation file to keep the annotation consistent. We will consider to add documentation about that and make new version of annotation file with info of data source.

Thanks for your comments.

ADD COMMENT

Login before adding your answer.

Traffic: 982 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