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
Possibly related to #6 (comment) . I successfully called neoloops in my sample using neoloop-caller. Adapting code from this repo's readme, I generated a Triangle plot of my region of interest, which consists of multiple segments of chr8 and chr14:
Two boxes at the apex of the Triangle are devoid of any Hi-C signal, even though neoloop-caller was able to identify loops in these regions. Looking at the Hi-C map of the locus in Juicebox, I see comparable interaction frequency with chr8 across the two segments of chr14:
Therefore, my conclusion is that Triangle is failing to plot the off-diagonal Hi-C signal for some SV segment pairs? Any guidance on this issue would be appreciated.
The text was updated successfully, but these errors were encountered:
Hi, sorry for not making this clearer in the documentation. By default, the plot_loops method perform a pooling algorithm on the input loop calls and only plot the strongest dots if multiple dots cluster in a local area. To switch this option off, just set the parameter "cluster" to "False" when you run plot_loops. Something like this:
Hi Xiaotao, thanks for the response and for this clarification, but I don't think it addresses the issue. I'm quite happy with the neoloop calls; these are far superior to FitHiC or HiCCUPS around this SV. However, the underlying Hi-C contact map seems to have gaps. Note that in the Triangle plot, the red Hi-C signal is entirely absent between the two segments containing MYC and OTX2. However, in the Juicebox visualization, it is quite clear that the red Hi-C signal is comparable in this region to adjacent regions.
Oh. NeoLoopFinder does have a procedure to automatically adjust the scale of Hi-C signals between different fragments, based on a regression model. If you prefer plotting the original signals, you can manually set the scale factor to 1 when you initialize the Triangle object. In your case, the command will be something like this:
Note that in this mode, you need to specify a value (in this case 1) to each pair of the fragments in the assembly, and the index of the fragment starts from 0.
Possibly related to #6 (comment) . I successfully called neoloops in my sample using neoloop-caller. Adapting code from this repo's readme, I generated a Triangle plot of my region of interest, which consists of multiple segments of chr8 and chr14:
Two boxes at the apex of the Triangle are devoid of any Hi-C signal, even though neoloop-caller was able to identify loops in these regions. Looking at the Hi-C map of the locus in Juicebox, I see comparable interaction frequency with chr8 across the two segments of chr14:
Therefore, my conclusion is that Triangle is failing to plot the off-diagonal Hi-C signal for some SV segment pairs? Any guidance on this issue would be appreciated.
The text was updated successfully, but these errors were encountered: