Skip to content
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

Feature/bridging graph environment #41

Closed
wants to merge 2 commits into from

Conversation

SridharJagannathan
Copy link
Collaborator

First version (not ready yet). Might be used something like this:

library(nat.flybrains)
shortest_bridging_seq(sample='DsecF', ref=JFRC2)
bg=bridging_graph(reciprocal = 1.01)
bg2=igraph::delete.edges(bg, 'DsecI|JFRC2')
bg2=igraph::delete.edges(bg2, 'DsecI|JFRC2')
bg2=igraph::delete.edges(bg2, 'DsecI|JFRC2')
bg2=igraph::delete.edges(bg2, 'JFRC2|DsecI')
bg2=igraph::delete.edges(bg2, 'JFRC2|DsecI')
plot(bg2)
nat.templatebrains:::set_bridging_graph(bg2, reciprocal = 1.01)
shortest_bridging_seq(sample='DsecF', ref=JFRC2)

Sridhar Jagannathan and others added 2 commits May 23, 2019 17:58
* coded with Greg
* can get/set ok BUT
* complication of what reciprocal argument must be specified
* also surgery on the graph is complicated by the fact that there may be 2 or even 4 edges between each pair of nodes.
@jefferis
Copy link
Contributor

I'm leaving this open for now, but this now feels a bit complicated and I think the likelihood is that we will be fine with the new #43 / #44 via argument to specify particular paths.

@jefferis
Copy link
Contributor

jefferis commented Oct 3, 2022

Closing as in the end we will not use this.

@jefferis jefferis closed this Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants