-
Notifications
You must be signed in to change notification settings - Fork 25
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
About n_interactions=0 error #10
Comments
Thank you for taking the time to report the issue. Having said that, the interactions in the matrix A_ij are meant to be i-->j. (I know it might be confusing and different implementations do it differently). I will double check that. Best F |
Hi @fabridamicelli , thanks for your reply:)
. |
Hi @joshua-shuhan, Thank you for following up and for the provided code. So running the code snippet that you provided leads to an activity matrix full of Best, |
Hi @fabridamicelli , Thanks for your reply. |
Hi @joshua-shuhan, I see your point, that makes sense. I could try to have a workaround for that case. But, in the meantime, I have another idea: Can you replace the 0 values by a very small value for the disconnected nodes in your connectivity matrix? Something like 1e-10, such that there is no division by zero error but still the influence is very small. I think that would be an interesting experiment to already check if your inference framework is doing "the right" thing. I'd be curious to see the results |
Hi! Thanks for creating this repo for simulating the Kuramoto model.
I generate random adj_mat and run the code. Some warnings came up, and I set these warnings as errors. The error message turns out as follows:
So I go check the code (in
kuramoto.py
) and find that then_interactions
term is the summation of adj_mat over its column (axis=0). However, as then_interactions
serves as the normalization term for the coupling term, should it be the summation of adj_mat over its row (axis=1)? Since A_{ij} represents the coupling effect from nodej
to nodei
.I am not sure if my thought is correct. If this bug is confirmed, I am happy to set a PR : )
The text was updated successfully, but these errors were encountered: