-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prior Knowledge: Integrate BioCypher #17
Comments
To keep track of the current state: the issue to create a networkx output adapter for BioCypher. I keep you updated, when this is implemented in BioCypher. |
@vicpaton @martingarridorc The NetworkX output adapter is merged: biocypher/biocypher#352 Currently, the workflow is to write a pickle of the NetworkX object to disk. Maybe it's worth considering an addition to do the transfer in-memory as well (as we do with the Pandas object). This could make the workflow of handover to the algorithm part of networkcommons more seamless. When using the NetworkX mode as described in the docs, BioCypher also writes an ingestion script as an accessibility tool for loading the object back into Python. |
great! this is very useful thanks @slobentanzer @nilskre |
@slobentanzer @nilskre do you think it would be possible to directly provide the networkx graph? It would allow better integration with the nc |
By directly you mean, that you have a BioCypher instance ( |
Yes, I think that would be most seamless. |
@nilskre yes, exactly! that would be great |
Alright, got it. Just created an issue in BioCypher to also make this use case directly possible. Until we have implemented this in BioCypher a fast workaround for your PoC, would be to directly access the networkx graph by the private attributes (not recommended for permanent use!)
|
The integration of BioCypher in NC should provide a graph (networkx or CORNETO graph) retrieved from various prior knowledge sources, including OmniPath.
The text was updated successfully, but these errors were encountered: