-
Notifications
You must be signed in to change notification settings - Fork 54
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
MLE% wackiness in input files #539
Comments
I tried fixing the register_restart routine, but it still doesn't correctly parse the:
The bug I had heard a rumor of is not this bug but something deeper. Just a note: openParameterBlock and closeParameterBlock don't now have a donotlog sort of option - it might be nice when used with parameter calls that are not logged. |
I think that I can reproduce something relevant in
but if I use this:
then I get the following error:
I am unsure if this is related to your error, which seems related to restart files, but it's certainly a rather serious error. |
Looks like
and explains why This is probably a file parser error, that is probably the next place to look. |
@kshedstrom I think this is fixed now, can we close it? |
Yes, fixed. |
If one uses MLE%USE_BODNER23, things behave as expected. Instead, the parameter_doc.short file lists it as:
with some other stuff in there. The problem is that the register_restarts routine for this only allocates some of the work arrays if MLE%UES_BODNER23 is True. This second check isn't checking for the MLE environment. Things then fail when the work arrays are used if not allocated.
The text was updated successfully, but these errors were encountered: