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
It's useful for the mesh_modifier tool to output the mask as either an ocean-mask (so 1 means ocean, and 0 means land) or as a land-mask (so 1 means land, and 0 means ocean). A simple command line option can easily be added to trigger between these two options.
The text was updated successfully, but these errors were encountered:
The part that converts to the ocean mask is this in modify_mesh_mask.py:
# Reshape landmask into the# elementCount dimension of the mesh file.# In the process overwrite self.file[var].ocnmask=np.logical_not(int(landmask[row, col]))
self.file[var][ncount] =ocnmask
So an argument just needs to be set in the option parser and then passed down to set_mesh_mask.
In talking with @slevis-lmwg he explained to me why you only change the MASK_MESH, and hence need the ocean grid for the mesh file.
What I will do is to check if this is needed for the SPARSE grid. It might not be, so we might not need this for that case, and hence, this will just lower the priority for this.
Another way to do this would be to output both a land mesh AND an ocean mesh file. That might be the best way for the most flexibility for the user, and without having to understand the options.
In talking with @mvertens we think this issue is of more relevance because her suggestion is that you set ATM_DOMAIN_MESH, LND_DOMAIN_MESH, and MASK_MESH all to the same mesh file for the sparse grid case. See #1731
It's useful for the mesh_modifier tool to output the mask as either an ocean-mask (so 1 means ocean, and 0 means land) or as a land-mask (so 1 means land, and 0 means ocean). A simple command line option can easily be added to trigger between these two options.
The text was updated successfully, but these errors were encountered: