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
Resolve m-number adjoint bugs introduced by 1855 #2194
Resolve m-number adjoint bugs introduced by 1855 #2194
Changes from 3 commits
83fd9ef
2dff39e
2230adb
514128e
ece6329
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.
Maybe just call it
change_m
?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.
It would be better to just add a boolean argument to
fields::use_real_fields
so that we can switch back to real fields without initializing. And then this could be called byfields::change_m_number
form ≠ 1
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.
At the very least, this needs to check that
new_m
is consistent with whether we have real fields and abort if not. Better yet, have it callif (new_m != 0) use_real_fields(false);
as noted above.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.
What do you envision
use_real_fields(false)
does in the case that the current simulation does have real fields (e.g. suppose originallym=0
but we are changing it tom=1
). Wouldn't we need to reinitialize everything?Or are you suggesting we refactor the initialization of the fields to
use_real_fields()
, such thatuse_real_fields(true)
deletes the extra array (the current behavior ofuse_real_fields()
)use_real_fields(false)
reallocates the fields if neededAs a first pass, it might be easiest to leave
use_real_fields
as is and simply ensure there's a proper check in place forchange_m_number()
(like you suggest).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.
My latest commit adds a check to make sure that the fields are consistent. If the user requests complex fields when the current setup is using real fields, I just abort.
This isn't a problem for the adjoint code. We have a similar check in the python routine. But rather than aborting, we just reinitialize.