You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From CTSM SE meeting today: Might be because single points should be thought of as POINTS, not gridcells. Effective gridcell size shouldn't give different answers. That's what's being done in subset_data.
Is there a better way to do this than having to enumerate every single point we want to do this for? Could do it in the build-namelist script instead. Have it set the mapalgo to nn if it's a single-point, as identified by nx and ny. (Can probably let 5x5amazon be bilinear.)
@ekluzek will add to this issue with an idea of how a solution might look.
samsrabin
removed
the
next
this should get some attention in the next week or two. Normally each Thursday SE meeting.
label
Jun 13, 2024
Various
mapalgo
settings are bilinear by default, with some single-point sites set to nearest-neighbor. It's not clear:popdensmapalgo
has some sites missing (e.g.,1x1_smallvilleIA
):CTSM/bld/namelist_files/namelist_defaults_ctsm.xml
Lines 1818 to 1825 in a943377
Same for
lightngmapalgo
:CTSM/bld/namelist_files/namelist_defaults_ctsm.xml
Lines 1724 to 1731 in a943377
Same for
urbantvmapalgo
:CTSM/bld/namelist_files/namelist_defaults_ctsm.xml
Lines 1877 to 1884 in a943377
lai_mapalgo
has some sites repeated (e.g.,1x1_brazil
) and some sites missing (e.g.,1x1_smallvilleIA
):CTSM/bld/namelist_files/namelist_defaults_ctsm.xml
Lines 1674 to 1687 in a943377
The text was updated successfully, but these errors were encountered: