About the value in bigwig file
0
0
Entering edit mode
17 months ago
Chris ▴ 340

Hi all, I want to compare the peaks to see which condition has more chromatin open and I got advice that I should adjust all the range to the highest value. When I set the min to 2.3, I got this. Is that the correct thing I should do in this case? Thank you so much.enter image description here

enter image description here

ATAC-seq • 1.1k views
ADD COMMENT
1
Entering edit mode

No, this doesn't make sense to me. For example your diseased Rep1 peak disappears, but it's clear there is a peak. So, this would be misleading to show it to anybody.

Maybe if you want to easily see peaks that pass a threshold, this could be okay to find the peaks, but be sure to use the full scale when presenting.

I usually just group autoscale all related tracks (or at least set the Max value to the same value) and then find peaks that are noticeable different enough.

ADD REPLY
0
Entering edit mode

It was autoscale as default and the value of each bigwig file still different. Or I don't have to change anything? Thank you.enter image description here

ADD REPLY
1
Entering edit mode

Underneath the check mark for Autoscale, there is a Group autoscale. That will group scale whichever tracks are currently selected.

ADD REPLY
0
Entering edit mode

Thank you so much! All tracks value after group autoscale now is 2.3. Could I say the disease is more open in this case?enter image description here

ADD REPLY
1
Entering edit mode

I might buy that if explained properly. If you zoom in on each region, you may be able to show the difference better.

ADD REPLY
1
Entering edit mode

Zoom into 63kb, I got something like this. I am not sure how much I should zoom in.

enter image description here

ADD REPLY
1
Entering edit mode

Probably depends on what point you want to make, but I think it looks nice.

ADD REPLY

Login before adding your answer.

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