You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the exon numbering for the reverse strand genes does not follow the commonly used exon numbering (5' to 3'). Instead, it forces exon numbering according to the forward strand, which can lead to misunderstandings. As an example, the exon numbering of the "FBgn0010909" gene shown in Figure 3, Chapter 6 of the vignette is reversed compared to ensemble.
I have investigated this issue and found two elements of the pipeline that cause this:
GenomicFeatures::exonicParts(txdb, linked.to.single.gene.only=TRUE) numbers exons solely according to the forward strand. I managed to manually reorder them with the simple self-written function shown below:
reorder.exons <- function(x){ #changing the order of the exons from the "-" strand
output <- x
temp_tab <- as.data.frame(x)
for(i in unique(temp_tab$gene_id)){
if(unique(temp_tab$strand[temp_tab$gene_id == i])=="-"){
indexes <- which(temp_tab$gene_id == i)
output@elementMetadata@listData$exonic_part[indexes] <- rev(output@elementMetadata@listData$exonic_part[indexes])
}
}
return(output)
}
Although I reordered it manually, your DEXSeqDataSetFromSE() wrapper tries to change it back in the further steps, causing an error. I used the DEXSeqDataSet() function directly as shown below and it seems to work fine now.
Based on the definition of the DEXSeqDataSetFromSE() function, I assume that the exon numbering according to the forward strand is intentional. Is there a reason for this? Please consider implementing reverse strand support in the next version of the package.
Kind regards,
Tomek
The text was updated successfully, but these errors were encountered:
Hi,
I noticed that the exon numbering for the reverse strand genes does not follow the commonly used exon numbering (5' to 3'). Instead, it forces exon numbering according to the forward strand, which can lead to misunderstandings. As an example, the exon numbering of the "FBgn0010909" gene shown in Figure 3, Chapter 6 of the vignette is reversed compared to ensemble.
I have investigated this issue and found two elements of the pipeline that cause this:
GenomicFeatures::exonicParts(txdb, linked.to.single.gene.only=TRUE)
numbers exons solely according to the forward strand. I managed to manually reorder them with the simple self-written function shown below:DEXSeqDataSetFromSE()
wrapper tries to change it back in the further steps, causing an error. I used theDEXSeqDataSet()
function directly as shown below and it seems to work fine now.Based on the definition of the
DEXSeqDataSetFromSE()
function, I assume that the exon numbering according to the forward strand is intentional. Is there a reason for this? Please consider implementing reverse strand support in the next version of the package.Kind regards,
Tomek
The text was updated successfully, but these errors were encountered: