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
currently debugging with ensmallen is hard as we just see CURIEs, no labels. It would be useful to have labels for multiple reasons:
sanity check/debugging
drop in networkx replacement
drop in rdflib replacement
ML methods that uses lexical information
OAK grape plugin
I appreciate ensmallen is built for speed, but what if this were an option, off by default, and it just built an ancilliary node index such that you could do
currently I am getting around this by wrapping grape and either using separate OAK objects to access node information, or by creating 2 graphs, a n2n graph and a n2literal graph
It would be useful to have the analogous operation on edges as in nx, i.e property graphs (there is a ton of useful information there in biolink graphs that should be used in ML - e.g. the frequency of d2p is v important). But this could be considered a separate feature request
The text was updated successfully, but these errors were encountered:
currently debugging with ensmallen is hard as we just see CURIEs, no labels. It would be useful to have labels for multiple reasons:
I appreciate ensmallen is built for speed, but what if this were an option, off by default, and it just built an ancilliary node index such that you could do
currently I am getting around this by wrapping grape and either using separate OAK objects to access node information, or by creating 2 graphs, a n2n graph and a n2literal graph
It would be useful to have the analogous operation on edges as in nx, i.e property graphs (there is a ton of useful information there in biolink graphs that should be used in ML - e.g. the frequency of d2p is v important). But this could be considered a separate feature request
The text was updated successfully, but these errors were encountered: