Closed wknoben closed 3 years ago
this is a good change ... there are a number of places where certain halts occur and wherever we can we should add the hruId/gruId to the error messaging. Often we're running grus in blocks and it's time consuming to identify the exact location of the halt.
this is a good change ... there are a number of places where certain halts occur and wherever we can we should add the hruId/gruId to the error messaging. Often we're running grus in blocks and it's time consuming to identify the exact location of the halt.
To give credit where it's due, this is the exact scenario I had when Martyn suggested making this change. Did you have any specific places in the code in mind where this addition could be helpful?
Updated the error reporting in routines
run_oneGRU
andrun_oneHRU
to include the index of the GRU in the netcdf file and the hruId. This is helpful when isolating problematic GRUs/HRUs in large domain runs.Example error before changes:
Example after changes:
Is this a desirable change? Are further checks of the code needed?