-
Notifications
You must be signed in to change notification settings - Fork 6
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
Gracefully handle nans in the input data #315
Labels
Comments
We already handle missing data, we should handle nans in the same way. |
Closing, as this is out-of-scope for our service. We assume that NANs will have been caught and pruned in the TA4 service. We can however return an error if we see NANs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This might be a problem for @fivegrant but if we receive nans in the dataset that is given to us, we shouldn't try to interpret it, we should instead drop those calibration events.
The text was updated successfully, but these errors were encountered: