Open ekluzek opened 6 days ago
This is in the same vein as #1913 and #144
Fixing this would just be adding dimexist options to the ncd_inqdid calls and check it.
This is something that should be done on b4b-dev. It's also the type of thing that having simple I/O testing would help with. So the functional test framework would be a good place for this to be tested in.
Brief summary of bug
I added a new restart variable, and used the dim1name of "patch" instead of "pft".
General bug information
CTSM version you are using: branch_tags/dustemisdev.n05_ctsm5.1.dev166-5-gf48830977
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: When adding new variables to the restart file
Details of bug
An example of where bad error messaging makes it hard to find problems in the code. I found the problem by pulling it up in DDT and then realized the issue when it came up on the define part, and not the write part. I thought it might have been because of bad data in the array to write, or the interpinic_flag.
Important details of your setup / configuration so we can reproduce the bug
Important output or errors that show the problem
The cesm.log does point to the error, but it's obfuscated enough with tons of output that it's hard to see.