Open billsacks opened 8 months ago
It seems like we can do option 1 now and then reevaluate whether we need to extend to 2 or 3.
Sounds good. I'm happy to do this. It's on my list for after I finish some ESMF work that may still take me another week or so.
Emerging from https://github.com/ESCOMP/CDEPS/issues/254 - we'd like for PIO to print the filename that leads to netcdf errors that are caught in the check_netcdf2 function. I'm happy to take this on (but I don't have permission to assign myself).
From a quick look through the code, it looks like most / all of the functions that call check_netcdf2 directly have a filename that they could pass in as an extra argument. Then I'm thinking that we'd modify the error message returned from netcdf to append the file name to the output message.
I'm not sure the best way to handle the call from check_netcdf to check_netcdf2. Options I see are:
I like the idea of (3), but I haven't looked into what it would involve. @jedwards4b do you have thoughts on whether this would be a reasonable solution?