FieldOutOfBoundError does not exit simulation#348
Merged
Merged
Conversation
erikvansebille
approved these changes
Jun 1, 2026
Member
There was a problem hiding this comment.
In v4 you may indeed want to do this more pythonic with dictionaries ({50: "Error", 51: "ErroInterpolation", ...})?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 on from #154 and discussion therein, this PR addresses
FieldOutOfBoundErrorsfor Argo Floats.Previously errors were captured via the
_check_error()kernel but this silently deleted particles (see #33 (comment)). Now, the kernel will print a warning so users at least know to expect incomplete data and can consider fixes.Closes #154