how do we store cooltools' outputs? One idea: inside cooler files

[golobor]

[golobor]

ping @nvictus - this would unblock the development of eigdecomp

[mimakaev]

I think this is not moving forward because we don't have a good definition of expected (by chr, genome-wide etc). Also, we're not sure about by-chromosome vs by-arm: what is better, and where to get centromere positions.

[Phlya]

Another related issue, open2c/cooler#122

[golobor]

we arrived to a solution, where external tools (including cooltools) are allowed to store their information as tables in groups /ext/<tool_name>.
@nvictus , do we need to take any further action to close this item? Maybe, a single line in the cooler schema?

[gfudenberg]

what about a cli command for cleaning the cooler's extra tables? "cooler purge tables" or "cooler refresh" , with options to keep specific keys (e.g. purge expected, but not weights from balancing)

…

On Mon, Jun 17, 2019 at 1:43 PM Anton Goloborodko ***@***.***> wrote: we arrived to a solution, where external tools (including cooltools) are allowed to store their information as tables in groups /ext/<tool_name>. @nvictus <https://github.com/nvictus> , do we need to take any further action to close this item? Maybe, a single line in the cooler schema? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#38>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEV7GZNTBT6OHUTSOF3IUYTP27ZNZANCNFSM4FTWPFSQ> .