-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use of undirected graph in plot_msm_network #110
Comments
@cxhernandez can speak to this more but my guess is that a directed graph would double the number of edges and would likely look very messy. For your side question, I dont think we have anything for that yet but I agree it would be a good idea. As a fast hack, you can clip the input transition matrix to be 0 below a certain threshold. Or maybe even feed in the clipped version of log10(matrix). |
Thanks for replying, I'll try the numpy clip! As for the undirected/directed, I just noticed it because I didn't see any self-connections in the node, which in turn are usually the biggest weight nodes for each microstate (at least in my simulations, that's usually the case). |
Yeah, it was to cut down on the complexity of the visualization because networkx makes ugly graphs. I'm very open to moving away from networkx plots and use something nicer. |
That's good to know then, I was just wondering if it was a small bug. I don't really know nice network plotting libraries for python, for the moment what I'm doing is saving the directed graph to disk with networkx and then inspecting it using Gephi or Cytoscape. |
Is there a reason why an undirected graph is built from the transition matrix in the
plot_msm_network
function?I've checked and the edges that are built when using an undirected graph do not match the entries of the transition matrix:
Also, as a side question: is there a way to hide the edges below a particular weight? When there are too many connections, the resulting plot is really crowded and is a bit confusing to look at.
The text was updated successfully, but these errors were encountered: