Skip to main content

From watershed to global

Ever since I finished my 3D ecosystem simulation using the ECO3D model, I started to think about applying this model to a larger spatial domain such as global.

While there are several technical difficulties in doing so, there are also different combinations of solutions to resolve these issues. In this post I will list out major issues we will address:

  • First, on a global scale, we need much more massive input data preparation. What's more, some traditional algorithm/method may not even work. For example, the watershed lineation process on global scale will not be used anymore. Instead, another river routing algorithm or dataset should be used.
  • File I/O will becomes an issue. Global scale simulation will use parallel computing, which mean the file I/O must support parallel reading/writing. Whether file system will be ideal or other options remains unclear. For example, can we use database or Hadoop?
  • Parallel computing with/without MPI/OpenMP. I am not sure of other options but running billion of instances on HPC requires parallel computing for sure. Maybe Hadoop or GPU could help.
  • Global grid system must be updated. Can we have a uniform grid scheme for simulation? With spatial relationship established, interactions among grids can be easier considered.
  • File storage. If data are not stored in database alike data server. A better storage approach will be used.

Because the ECO3D is finally released, my next research focus will be applying it to a large spatial domain. The following steps should be taken in sequence:
  1. Add MPI capability to the ECO3D model. Currently it only uses OpenMP for a watershed scale. On a global scale, MPI is an inevitable path;
  2. Develop the DGGS for the spatial discretization scheme;
  3. Design a better storage system for file I/O.
  4. Develop a GDAL-based raster/vector dataset tool, this tool will be used to speed up all geospatial dataset operations.
I am also looking forward to working with collaborators.


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…