-
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
coerce correct tensor datatypes #567
Comments
@mwdchang , could you please share the AMR that was used to generate this error? I'd like to include that in the tests when we resolve this issue. Thanks! |
@SamWitty I am just passing on the error from Pascale so the exact circumstance of how the error was generated may need to be taken with a grain of salt. From what I can gather, this is a a simulation with params in the following structure:
And the corresponding model is the one attached below: |
Hi folks, it appears that this error occurs when you provide a long instead of a float. We have some tooling for catching these issues, but maybe we need to do some more robustifying. |
It would be nice if the library can coerce to the datatypes it wants to use, so at the input level we don't need to explicitly distinguish between integers, longs, floats ... etc.
This is one instance of an error trace we saw, where there was a type mismatch (probably the population number) of a long-type but the lib wants a float-type:
The text was updated successfully, but these errors were encountered: