Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Occupancy plot: observed and fitted occupancy differ #44

Closed
ShaluJhanwar opened this issue Aug 17, 2016 · 2 comments
Closed

Occupancy plot: observed and fitted occupancy differ #44

ShaluJhanwar opened this issue Aug 17, 2016 · 2 comments

Comments

@ShaluJhanwar
Copy link

ShaluJhanwar commented Aug 17, 2016

Hi Alicia,

I am running NucleoATAC to identify nucleosome from ATAC-seq data. I looked at the *occ_fit.eps plot given by NucleoATAC. The observed and nucleosome fit is really different as shown in the plot:
nuc_dist
occ_fit
Vplot

i) I wonder it is not fitting properly on the observed data. Could you please suggest to tune some parameter to make fitting properly on the observed data? I have pooled the 16 ATAC samples and run nucleoatac run command with default params.

ii) I found approximately 511590 nucleosomes and only 5278 nfr regions as a result of above fitting. Do you think it's correct estimate for numbers of nucpos and nfr region in mouse genome, and positions as well?

Thanks!
Shalu

@ShaluJhanwar
Copy link
Author

Hi Alicia,

In addition to above details, the global fragment size distribution of one of the 16 samples looks like: globalfragmentSizeOneSample

Shalu

@AliciaSchep
Copy link
Contributor

The fitting is a bit tricky here because there seems to be a big overlap between NFR and nucleosome distributions (not a clear separation between those two peaks). Seems to be doing something reasonable given the distribution though

As for the numbers, two things to keep in mind:

  1. The nucleosome calling should not be considered comprehensive -- the goal is to find positions where there is evidence of nucleosome positioning from ATAC, but ATAC will not provide adequate coverage when linkers are not very accessible (restricting analysis to peaks helps, but even within the peak regions there may be insufficient coverage throughout).

  2. The NFR calling is finding NFR regions bounded by two called nucleosomes and is thus subject to the limitations in (1). In a development branch of NucleoATAC (NFR) this limitation is limited so that NFRs can be called even when we can't confidently call flanking nucleosomes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants