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
The method ExplicitNetworkGenerator.generate_network_from_names(components, names) only includes nodes (components) that are connected by edges. i.e., no unconnected/floating nodes are included. This is in contrast to the current openfe network generating behavior.
I noticed this when unit tests for this openfe PR failed, because ligand_network_planning.generate_network_from_names() is being switched to use konnektor's ExplicitNetworkGenerator implementation.
@IAlibay I believe we should change the Konnektor implementation to match the current openfe behavior. However, I'd like to know if this was intentionally done by @RiesBen as part of Konnektor's design.
The text was updated successfully, but these errors were encountered:
@atravitz
hi, jap I wanted that behavior, as I wanted konnektor to not return disconnected networks by default. But maybe simply throwing an error would have been wiser?
I think this needs discussion, but disconnected networks is something we will likely want under certain circumstances. I remember the original behaviour was somewhat of an intentional design decision (although I had asked that it threw at least an error to let folks know the network was disconnected).
Describe the bug
The method
ExplicitNetworkGenerator.generate_network_from_names(components, names)
only includes nodes (components) that are connected by edges. i.e., no unconnected/floating nodes are included. This is in contrast to the current openfe network generating behavior.I noticed this when unit tests for this openfe PR failed, because
ligand_network_planning.generate_network_from_names()
is being switched to use konnektor'sExplicitNetworkGenerator
implementation.To Reproduce
This Konnektor unit test demonstrates this.
Expected behavior
@IAlibay I believe we should change the Konnektor implementation to match the current openfe behavior. However, I'd like to know if this was intentionally done by @RiesBen as part of Konnektor's design.
The text was updated successfully, but these errors were encountered: