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

Insertions and coverage tracks #39

Closed
DoaneAS opened this issue Jun 20, 2016 · 4 comments
Closed

Insertions and coverage tracks #39

DoaneAS opened this issue Jun 20, 2016 · 4 comments

Comments

@DoaneAS
Copy link

DoaneAS commented Jun 20, 2016

Hi,
Thanks for these tools, they are very useful!

Just a few quick questions I couldn't find in the documentation.

For the insertion frequencies, returned form pyatac ins
are these values normalised to total number of insertions? The documentation says frequencies, but it's not clear to me what the denominator is.

likewise for pyatac cov, are the values normalised to total number of fragments in the bam file?

thanks

Ashley

@AliciaSchep
Copy link
Contributor

The values are not normalized to the total number of fragments in the bam files. I think that for the ins the value should just be the per base integer counts (unless smoothed). For the cov the scaling is fragment centers within a window divided by the window size, multiplied by an arbitrary scaling factor that can be chosen (default is 10, meaning the value is equivalent to fragment centers per 10 bp). You could make this scaling factor related to the total read count if you want to normalize by that

@DoaneAS
Copy link
Author

DoaneAS commented Jul 9, 2016

Thanks for explaining and for the helpful suggestion. I have been using the smoothed ins tracks (using a window of 121) as an alternative to typical coverage tracks (from macs2 output for example), so that the insertion sits are more faithfully represented. I would be curious to know what you recommend for atac insertion density tracks to represent accessibility.

So if I understand the output of cov correct, "fragment centers" means the position centered between the Tn5 insertion sites?

Thanks!

@AliciaSchep
Copy link
Contributor

Yes the fragment centers means the position that is halfway between the Tn5 insertion sites. This is more similar to a typical coverage plot in which you would consider the contribution of an entire fragment, except that for every fragment a set number of bases around the center contribute to the coverage rather than the whole fragment.

I agree with you that for representing accessibility that the smoothed insertion track makes mores sense than either the typical coverage plot or the modified coverage plot computed by "cov", as it is really the insertion points and not the middle of some fragment that represents the regions that are accessible.

@DoaneAS
Copy link
Author

DoaneAS commented Jul 11, 2016

Many thanks Alicia!

@DoaneAS DoaneAS closed this as completed Jul 11, 2016
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