Samuel Levis

From today's emails so that I don't lose track... @adamrher wrote: The status is that it does what we want it to do -- it flags the bad grid, and...

The new mksurdata_esmf has been pointing to the new transient lake files. However, it has NOT been pointing to the new baseline lake files for time-slice simulations. To correct this...

For mksurfdata_esmf to generate fsurdat files for time-slice cases using the new lake files, I had to add the variable LAKEDEPTH to the year-2000 and year-1850 lake files. For simplicity...

This [post earlier in this issue](https://github.com/ESCOMP/CTSM/issues/1106#issuecomment-679901689) suggests that files already existed for time-slice cases, so I will point to those.

> This [post earlier in this issue](https://github.com/ESCOMP/CTSM/issues/1106#issuecomment-679901689) suggests that files already existed for time-slice cases, so I will point to those. Discussed this with @ekluzek who expressed concern about consistency...

From 2022/9/22 software meeting: @billsacks asked and I confirmed that LAKEDEPTH in the three baseline files 1850, 1900, 2017 is identical. With this in mind, the recommended solution is to...

> [...] the recommended solution is to [...] always read PCT_LAKE from the transient files. This is now done in #1732

This was addressed in #1732 so I'm closing this issue.

I would not close as a wontfix for now. Let's first see how the cssi project makes use of the fsurdat_modifier tool. This may give us insight into whether we...

@adrifoster recommended checking the xarray versions on cheyenne (where fsurdat_modifier works) vs. izumi (where fsurdat_modifier generates a malformatted .nc file). I see differences in `libhdf5, libnetcdf, xarray, h5py` that seem...