Skip to content
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.

Sign up for GitHub

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

Jump to bottom

On a failed solve, check whether the input was NaN as well #81

Open
patrick-kidger opened this issue Feb 8, 2024 · 0 comments
Open

On a failed solve, check whether the input was NaN as well #81

patrick-kidger opened this issue Feb 8, 2024 · 0 comments
Labels
next Higher-priority items refactor Tidy things up

Comments

@patrick-kidger
Copy link
Owner

Sometimes we detect that the output was NaN, and fail the linear solve. Under these circumstances we should check whether the input had any NaNs as well -- indicating that the culprit was probably something upstream.

Inspired by patrick-kidger/diffrax#368.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
next Higher-priority items refactor Tidy things up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@patrick-kidger