Skip to main content

The life span of a project


Recently I have been working on a project that I need to prepare some maps. I had to go back to use some code I wrote almost 5 years ago. Then I realized that this happened to me many times.

I once read a line saying "If you think you are going do this again in the future, you should write a code for it". This is pretty much the major reason that drivers me to write lots of codes.

Sometimes I write code for fun, to demonstrate or test some ideas. (Which I plan to share some example in another post). For example, I wrote a program to test different method for carbon cycle using Explicit method or matrix method (Link).

But for most time, I wrote code so I don't have to manually do something. Just image if you have to open 10k excel files to do some simple math!

(I never wanted to write a programming language, at least for now. Most of my codes work to solve a real world problem.)

And more importantly, I always look ahead.

For example, if I decide to write a program to calibrate model, I try NOT to write one just for one model. I will write one such program for ALL models. So that in the future, if I work on a different model, I can re-use the program I wrote. (I actually have already finished a PEST based Python tool for all model calibration.)

That pretty sums up my my status: I constantly rely on efforts that I spent many years ago.

Because when you invented something, you don't know when will you use it in the future.

But reality does not work that way. You may change institutes, universities, projects.

A project usually lasts for a couple of years, how can we justify that what we are doing right now ONLY supports the project we are working on? Apparently that the benefit of some effort might be much longer than we originally expected.

In another way, the training of a profession lasts for a long time. What we do right may not contribute directly to our current projects and institute, only if you stay for a long period of time. For example, lots of work I do right now benefit from my work in PhD, Purdue University.

As a researcher, I want to build my knowledge tree/pyramid around my field. In Earth science, that basically means I have to acquire lots of skills: ecosystem, biology, hydrology, geology, GIS, remote sensing, computation, HPC, etc. And that is a lifetime task. But definitely as I patch the map piece by piece, the big picture becomes clearer and clearer.

To summarize, if you plan to do something in the long run, build it not just for now, but for the foreseeable future.





Comments

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.,

https://www.researchgate.net/post/What_does_one_mean_by_Model_Spin_Up_Time

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.
https://en.wikipedia.org/wiki/Initial_value_problem
https://en.wikipedia.org/wiki/Boundary_value_problem

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…

Watershed Delineation On A Hexagonal Mesh Grid: Part A

One of our recent publications is "Watershed Delineation On A Hexagonal Mesh Grid" published on Environmental Modeling and Software (link).
Here I want to provide some behind the scene details of this study.

(The figures are high resolution, you might need to zoom in to view.)

First, I'd like to introduce the motivation of this work. Many of us including me have done lots of watershed/catchment hydrology modeling. For example, one of my recent publications is a three-dimensional carbon-water cycle modeling work (link), which uses lots of watershed hydrology algorithms.
In principle, watershed hydrology should be applied to large spatial domain, even global scale. But why no one is doing it?  I will use the popular USDA SWAT model as an example. Why no one is setting up a SWAT model globally? 
There are several reasons we cannot use SWAT at global scale: We cannot produce a global DEM with a desired map projection. SWAT model relies on stream network, which depends on DEM.…