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.
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
Classes for making standard monitor functions #114
Classes for making standard monitor functions #114
Changes from 16 commits
770292f
2ba8628
ee54b3f
d44fbef
c9d6caf
2187d07
f66e7c0
4f12b6b
49a4d15
0da2be1
c393aa5
3aa4e3d
2aacae8
1432347
5c27f6c
dfb651f
5d7d116
8e94b1e
9cda85f
62dfbce
dc0a7b1
a6636e0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I have a feeling that using
radius=np.sqrt(0.15)
might be confusing and lead people to think they need to input the sqrt of the radius. Why not just input e.g.radius=0.4
?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.
Addressed in 9cda85f.
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.
Thanks! But the optimisation callback should be updated too. It looks like this now:
Quite a few more iterations (up from 52 with
np.sqrt(0.15
) since it gets stuck a bit as you can see.This also made me wonder - where did the solver parameters in
movement.solver_parameters
come from?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.
Updated in a6636e0 using output from my machine. I imagine it's due to how the initial mesh is lined up, but would need to investigate in more detail. Opened a new issue: #148.
The ones for MA are based on the ones in Andrew McRae's 2018 paper.