Replies: 1 comment
-
Hi Kirk, yes, there are excess rows. You can get rid of them with something like the following: final_states["eCa"][cell._internal_node_inds] The reason for the excess rows is that, internally, I think I agree we should remove these states by default (when running Michael |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When producing a final_states output using:
the returned output contains 94 excess rows/components (approx 15% of my valid jaxley computed components total). The excess rows have (default?) state values of -1, with some 0. The first n rows accord with my model number of components, values are approx as expected, and model is working roughly as expected, so not sure what could be causing this output, and how it may affect computation.
Attached an extract, last few valid rows, then first few excess rows, further excess rows are identical.
extra segments example.ods
Beta Was this translation helpful? Give feedback.
All reactions