You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your work. I used armatus to call TADs in my genome, and a consensus TAD table was produced at a resolution of 40kbps. I noticed that many TADs are closely adjacent, like shows below:
How should I distinguish TAD boundries from this? Is there 15 distinct TADs, or should i merge adjacent TADs like LG01 2680000 2759999 and LG01 2760000 2879999 together into a large TAD as LG01 2680000 2879999?
Is that means the region between two non-adjacent TADs, like the region between LG01 880000 959999 and LG01 1080000 1199999, is a TAD boundry, or no matter how large it is, all regions between calculated TADs should be treated as TAD boundries? In another word, should LG01 2320000 2399999 and LG01 2400000 2479999 has a TAD boundry of 0 bps, or should the two adjacent region just be treated as a large TAD without considering any boundries in it?
Thank you!
The text was updated successfully, but these errors were encountered:
Hi team,
Thank you for your work. I used armatus to call TADs in my genome, and a consensus TAD table was produced at a resolution of 40kbps. I noticed that many TADs are closely adjacent, like shows below:
LG01 2680000 2759999
andLG01 2760000 2879999
together into a large TAD asLG01 2680000 2879999
?LG01 880000 959999
andLG01 1080000 1199999
, is a TAD boundry, or no matter how large it is, all regions between calculated TADs should be treated as TAD boundries? In another word, shouldLG01 2320000 2399999
andLG01 2400000 2479999
has a TAD boundry of 0 bps, or should the two adjacent region just be treated as a large TAD without considering any boundries in it?Thank you!
The text was updated successfully, but these errors were encountered: