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
However, the identical node present in both sets has a self loop in phenos1 and no connection to phenos2.
Diagnosis: this comes down to how graph joins work in tidygraph (which is natural, over all matching columns) when the two node sets disagree in one of the columns. I think the desired behavior is right and desired with respect to that, we're just not keeping the original node sets properly in creating the join.
The text was updated successfully, but these errors were encountered:
oneilsh
changed the title
monarch_semsim doesn't handle identical ID phenotypes with
monarch_semsim doesn't handle identical ID phenotypes well
Aug 5, 2024
This example should produce two pairs of nodes best matching each other in both directions:
However, the identical node present in both sets has a self loop in phenos1 and no connection to phenos2.
Diagnosis: this comes down to how graph joins work in tidygraph (which is natural, over all matching columns) when the two node sets disagree in one of the columns. I think the desired behavior is right and desired with respect to that, we're just not keeping the original node sets properly in creating the join.
The text was updated successfully, but these errors were encountered: