Merging files with different normalizations and resolutions into a single .hic/.mcool file #306
-
Hi |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Hi! We do not provide such functionality because it would not be trivial to prevent users from creating broken files by providing incompatible inputs to hictk. Can you elaborate a bit on what your use-case for such functionality would be? |
Beta Was this translation helpful? Give feedback.
-
Thank you for your quick response. Let me explain the actual problem I need to solve in detail. Currently, I have generated 5kb (A_5kb.hic), 10kb (A_10kb.hic), and 20kb (A_20kb.hic) hic files using hictk. Additionally, I have normalized these hic files, resulting in files such as A_5kb_ice.hic, A_10kb_ice.hic, A_20kb_ice.hic, A_5kb_scale.hic, A_10kb_scale.hic, and A_20kb_scale.hic. May I ask, how can I use hictk's merge functionality to combine these 9 files into a single hic file? |
Beta Was this translation helpful? Give feedback.
-
Thanks for providing more details. I think what you are trying to do can be achieved as follows:
In practice: hictk load interactions.pairs.gz -f 4dn A_5kb.hic --bin-size 5000 # This you already have
hictk zoomify A_5kb.hic A_multires.hic --resolutions 5000 10000 20000 # You can also not specify resolutions and let hictk generate some default ones for you (see docs for `--nice-steps` and` --pow2-steps`)
hictk balance ice A_multires.hic --force # --force is needed because you have already balanced the base resolution, and so you need to tell hictk to overwrite existing weights
|
Beta Was this translation helpful? Give feedback.
-
Can hictk generate a .hic file that contains ICE, scale, and raw statues? |
Beta Was this translation helpful? Give feedback.
-
Yes it can! You can balance the same file (regardless of the format) with different algorithms (and even different variants of the same algorithm). In your specific case, simply run |
Beta Was this translation helpful? Give feedback.
Hi!
We do not provide such functionality because it would not be trivial to prevent users from creating broken files by providing incompatible inputs to hictk.
Can you elaborate a bit on what your use-case for such functionality would be?
Is it something that cannot be achieved with a combination of
hictk load/merge zoomify and balance
?