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
wijk += pow(Graph(i, a) * Graph(i, b) * Graph(a, b), 1.0 / 3); //wij + wik
, it appears that the edge weights are being added rather than multiplied as described in the associated paper. If this is the case, I am curious to know the reason for this change.
if (f * max(OTSU, total_factor) > cluster_factor[49].score)
{
f -= 0.05;
}
else {
break;
}
}
for (int i = 0; i < Graph.rows(); i++)
{
if (Match_inlier[i] && cluster_factor_bac[i].score > f * max(OTSU, total_factor))
, I am unsure about the purpose of lines 664-673. Is it possible that the final value of f * max(OTSU, total_factor) is very similar to cluster_factor[49].score? Would it be possible to use cluster_factor[49].score directly instead? Additionally, this section of code appears to only retain the top 50 vertices, which may result in a very sparse compatibility graph. Could you please provide some insight into the reasoning behind this design choice?
The text was updated successfully, but these errors were encountered:
qiaozhijian
changed the title
Two questions regarding the code
Three questions regarding the code
May 26, 2023
Your questions are about the dynamic adjustment of the compatibility graph scale. Let's suppose that the inlier ratio of the input correspondence set is high, then the compatibility graph will be dense, making searching for maximal cliques in the whole graph more time-consuming. Based on this, we introduce the clustering coefficient to measure the density of the compatibility graph. Please refer to our previous work mutual voting for ranking 3D correspondences. If the coefficient is large, we choose to reduce the size of the compatibility graph, that is, only retain the nodes with higher weights and the edges formed by these nodes. Note that the mechanism is not mentioned in our paper, because: 1) it is not our main innovation point; 2) the operation of reducing the graph size will only take effect when the inlier ratio is high.
Thank you for your excellent work! I have three questions regarding the code.
Firstly, in the code located at this link:
3D-Registration-with-Maximal-Cliques/Linux/registration.cpp
Line 523 in f85cc3e
Secondly, in the code located at this link:
3D-Registration-with-Maximal-Cliques/Linux/registration.cpp
Line 1160 in f85cc3e
3D-Registration-with-Maximal-Cliques/Linux/funcs.cpp
Line 551 in f85cc3e
Thirdly, in the code located at this link:
3D-Registration-with-Maximal-Cliques/Linux/registration.cpp
Lines 664 to 676 in f85cc3e
The text was updated successfully, but these errors were encountered: