Structure of DiffBind dba.count matrix equivalent to DESeqDataSetFromMatrix input?
1
0
Entering edit mode
rbronste ▴ 60
@rbronste-12189
Last seen 5.0 years ago

Wondering if the basic matrix output from dba.count in DiffBind would be an appropriate input matrix into DESeq2 (via DESeqDataSetFromMatrix) or if has to be modified in some other fashion? I want to run DESeq2 interactions on this interval read count matrix generated by DiffBind. Thank you.

deseq2 diffbind • 1.4k views
ADD COMMENT
1
Entering edit mode
Rory Stark ★ 5.2k
@rory-stark-5741
Last seen 4 weeks ago
Cambridge, UK

Yes this can be used to create a DESeqDataSet object. You have to pay attention to the score, which should be DBA_SCORE_READS (or, more controversially, DBA_SCORE_READ_MINUS). You can change an existing score without recounting by calling dba.count() with peaks=NULL, then retrieve the counts using dba.peakset():

> myDBA <- dba.count(myDBA, peaks=NULL, score=DBA_SCORE_COUNTS)
> rangedCounts <- dba.peakset(myDBA, bRetrieve=TRUE)

If you want the counts by themselves (without the site interval ranges) in a matrix (for use in DESeqDataSetFromMatrix) :

> counts <- as.matrix(mcols(rangedCounts))

 

ADD COMMENT
0
Entering edit mode

Thanks for the info Rory! Thats pretty much what I have been doing. Is there a good way on the back end, once I do whatever interaction analysis with DESeq2, to quickly interrogate specific intervals (differential/interacting ones I find interesting) when the site interval ranges are removed from the matrix I am inputting into DESeqDataSet?

I guess with genes and transcripts its easier since you have the identifier/name. I guess they still have the first numbered column of the matrix.

ADD REPLY
0
Entering edit mode

Wondering if its possible to return the dba.peakset as a RangedSummarizedExperiment object?

ADD REPLY

Login before adding your answer.

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