Skip to main content

A visual decomposition of the land grid in the E3SM/CESM model

One of my recent development projects needs to exchange several variables between different components using the Common Infrastructure for Modeling the Earth (CIME) model. However, different components have different grid systems. Therefore, I have to get familiar with the grid system of these two component before assigning any variables.

One of them is the land grid used in Community Land Model (CLM)/ELM, which is the land component in the Energy Exascale Earth System Model (E3SM) model. Because CLM is also part of CESM, this post should also apply to the CESM land component.

In short, the land component distributes all the land units across multiple nodes/cores and each grid cell is run by clump.

Here I developed a small Python utility to illustrate the concept.

First we define a sample problem as follow:

Core per CPU
Segment per clump
Core count
Longitude count
Latitude count
Land count

Then we define the global grid and land mask:

Before you start to read the numbers, you need to understand the index system used in E3SM.
Even though Fortran is a column-major language, the E3SM (written in Fortran) stores the global grid using a row-major approach. As a result, global grid index starts from left to right in memory, same as the land mask (Figure 1).

Note that yellow square represent clump index, blue square represent land index, and red square represents global grid index.
Figure 1. The global ID and land ID map.

Similar to global grid, clump/core index starts from left to right across node/processor. For example, clump 1 is located on the first core on processor 1 and clump 2 is located on the first core on processor 2.

Last, we distribute the land grid onto the clumps. All the land grids are allocated to clump in order. In the end, a clump may simulate multiple land grids which are far away in the spatial domain. For example, the clump 1 simulates land grid 1, 41 and 81 (circled in yellow in Figure 1 and 2).

Figure 2. The processor, clump and land grid decomposition.

The global grid and land grid is connected through the “gdc2glo” variable, which stores what is the land grid index for each clump in order. For example, gdc2glo[1] = 125 means that the 125th global grid is the “second” (index starting from 0) simulated land grid, which is land grid 41.

Let me know if you have any question.


Popular posts from this blog

Spatial datasets operations: mask raster using region of interest

Climate change related studies usually involve spatial datasets extraction from a larger domain.
In this article, I will briefly discuss some potential issues and solutions.

In the most common scenario, we need to extract a raster file using a polygon based shapefile. And I will focus as an example.

In a typical desktop application such as ArcMap or ENVI, this is usually done with a tool called clip or extract using mask or ROI.

Before any analysis can be done, it is the best practice to project all datasets into the same projection.

If you are lucky enough, you may find that the polygon you will use actually matches up with the raster grid perfectly. But it rarely happens unless you created the shapefile using "fishnet" or other approaches.

What if luck is not with you? The algorithm within these tool usually will make the best estimate of the value based on the location. The nearest re-sample, but not limited to, will be used to calculate the value. But what about the outp…

Numerical simulation: ode/pde solver and spin-up

For Earth Science model development, I inevitably have to deal with ODE and PDE equations. I also have come across some discussion related to this topic, i.e.,

In an attempt to answer this question, as well as redefine the problem I am dealing with, I decided to organize some materials to illustrate our current state on this topic.

Models are essentially equations. In Earth Science, these equations are usually ODE or PDE. So I want to discuss this from a mathematical perspective.

Ideally, we want to solve these ODE/PDE with initial condition (IC) and boundary condition (BC) using various numerical methods.

Because of the nature of geology, everything is similar to its neighbors. So we can construct a system of equations which may have multiple equation for each single grid cell. Now we have an array of equation…

Lessons I have learnt during E3SM development

I have been involved with the E3SM development since I joined PNNL as a postdoc. Over the course of time, I have learnt a lot from the E3SM model. I also found many issues within the model, which reflects lots of similar struggles in the lifespan of software engineering.

Here I list a few major ones that we all dislike but they are around in almost every project we have worked on.

Excessive usage of existing framework even it is not meant to Working in a large project means that you should NOT re-invent the wheels if they are already there. But more often, developers tend to use existing data types and functions even when they were not designed to do so. The reason is simple: it is easier to use existing ones than to create new ones. For example, in E3SM, there was not a data type to transfer data between river and land. Instead, developers use the data type designed for atmosphere and land to do the job. While it is ok to do so, it added unnecessary confusion for future development a…