-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow custom jaxley
solvers to have different nseg per branch
#426
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaeldeistler
changed the title
copy over code from new version of different-nseg
Allow custom Sep 19, 2024
jaxley
solvers to have different nseg per branch
michaeldeistler
force-pushed
the
different-nseg-for-custom2
branch
9 times, most recently
from
September 20, 2024 18:05
c668807
to
9e782e3
Compare
michaeldeistler
force-pushed
the
different-nseg-for-custom2
branch
from
September 20, 2024 18:23
d16c894
to
54b45a5
Compare
This was referenced Sep 21, 2024
Closed
michaeldeistler
force-pushed
the
different-nseg-for-custom2
branch
6 times, most recently
from
September 23, 2024 22:01
c501d08
to
ff736a3
Compare
jnsbck
approved these changes
Sep 23, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice refactor. I like the line diff! 🗡️ Left a few comments. If tests pass and there are no issues, good to go from my side.
michaeldeistler
force-pushed
the
different-nseg-for-custom2
branch
2 times, most recently
from
September 23, 2024 23:07
8d449de
to
dfdc887
Compare
michaeldeistler
force-pushed
the
different-nseg-for-custom2
branch
from
September 23, 2024 23:09
dfdc887
to
62f8561
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following #418, this will also allow different nseg per branch for the jaxley.thomas solver. This works by masking the tridiagonal system in every branch.
In addition, it also uses more invasively
.comp_edges
to build the conductances of the custom solver more easily. Before this PR,.comp_edges
had only been used for thejax.sparse
solver.Replaces #425 which was closed due to difficult merge conflicts.
In addition, this contains a bugfix and closes #429.