We are currently using the same elevation for all lakes in the pipeline here. This doesn't make a big difference for GLM, but it is/was always an oddity and a shortcut. Now that elevation is a predictor in the EA-LSTM (another downstream user of this pipeline), I assume we'll want to add it here and use it in the H_A_ list that is used to set the hypsography in the nml.
This was done for all CONUS lakes > 4ha here, which uses a scipiper tasktable within the function (see here) to make tile-based calls, similar to how we did the GCM work (but in this case, it wasn't w/ targets).
We are currently using the same elevation for all lakes in the pipeline here. This doesn't make a big difference for GLM, but it is/was always an oddity and a shortcut. Now that elevation is a predictor in the EA-LSTM (another downstream user of this pipeline), I assume we'll want to add it here and use it in the
H_A_list that is used to set the hypsography in the nml.This was done for all CONUS lakes > 4ha here, which uses a
scipipertasktable within the function (see here) to make tile-based calls, similar to how we did the GCM work (but in this case, it wasn't w/targets).