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

Save stats in coolers #90

Open
Phlya opened this issue Feb 7, 2018 · 2 comments
Open

Save stats in coolers #90

Phlya opened this issue Feb 7, 2018 · 2 comments

Comments

@Phlya
Copy link
Member

Phlya commented Feb 7, 2018

Hi, I was thinking it would be cool if stats about the experiment could be saved directly into the cooler files too (in metadata/info?). This would make this information be always associated with the cooler file, no need to calculate cis/trans since the information is already there, and would in general make comparing multiple experiments easier since everything is easily accessible from python.

@golobor
Copy link
Member

golobor commented Feb 12, 2018

hmmm, that's a good idea. @nvictus, any thoughts?
Transferring pairs-level stats into coolers may be a bit clumsy, since it'll add one more command-line flag to type and one more file to track. Ideally, stats should be stored in the header of a pairs file and then get transferred to .cool files. But with .pairs files currently being a single text file, the implementation will be slow. I think storing stats in the header will get more natural once we switch to the binary storage format for pairs.

The current alternative is to expand calculation of statistics in cooler. Specifically, we can add cis/trans, scalings, chromosome-vs-chromosome counts, etc. @Phlya, @nvictus what do you think?

@Phlya
Copy link
Member Author

Phlya commented Feb 12, 2018

I agree that if stats are stored in a separate file it becomes a little complicated, and if they were in the header it would be much simpler.

The alternative idea sounds good to me - and these stats could also then be calculated at creation of the cooler file (optionally?) and stored in it.

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