-
Notifications
You must be signed in to change notification settings - Fork 57
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
Assertion failed error #1011
Comments
yup that's the same issue as #1009 It was accidentally added by me as a consequence of making other errors nicer for julia (specifically turning them into runtime rather than compile time errors). So it is in some sense now fixed by the linked PR, but unfortunately will require a JLL. bump to land here with the update before you can use it from Julia. |
Amazing! I'll hold off on working on it until that update happens then. Is my understanding correct that I don't need to make a MWE in this case? |
Correct! If you want to try it early you could use that custom jll process, but it's probably just easier to wait for the next bump. cc @vchuravy |
bumped jll, please retry! |
Just retried my code and got a different error:
I've seen this before, messing around with the code that led to it is how I found the assertion error. Could you offer insight into what this one might be saying? I can't really tell what the error message actually is |
weird, open a new issue? cc @vchuravy |
There's an ocean model I'd like to be able to use with Enzyme, but I've been hitting an "assertion failed" error early on in the integration function. I've been working on creating a MWE but it's a bit tricky as there are a lot of moving parts. I'll continue working on it, but in the meantime I thought I'd post the error in the hopes you might know more about what's going on. I saw someone else posted an issue that looked similar to what I've been seeing, at least to someone who doesn't develop Enzyme. I'm attaching the output as a text file as it's quite long
error_advection_coriolis_only5.txt
The text was updated successfully, but these errors were encountered: