-
Notifications
You must be signed in to change notification settings - Fork 217
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
Background Fields: Fix Restart GUARD #2139
Background Fields: Fix Restart GUARD #2139
Conversation
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.
Looks good to me - but let us perform a run time test.
f3d1c21
to
fd795b0
Compare
Simplify the logic of restarting fields: - do not add the already contained fields in `movingWindowCheck` again - spares us the substraction we had before - GUARDS are not part of the checkpoint data, which is cumbersome for the "outer" GUARDS of our global domain - we need to add the background field ONLY in those to generate a valid restart field
fd795b0
to
494865e
Compare
I verified this fix with the field background example from #2137. I used only the field background for the E field. |
@ax3l l see above for the backport to 0.3.0 - it is the last commit |
@BeyondEspresso please take note of this bugfix fo restarts with background fields if you have not seen it yet. also applies to (all) previous releases! (sorry :( ) included since we added the field background to the plugins (for you ;) ) |
Guys, this is awesome! 😃 Great work, all of you! 🥇 |
(Trying) to close #2137:
Restart of background fields could cause:
Simplify the logic of restarting fields:
movingWindowCheck
again