The CLM also allows you to set up and run cases with a single-point or a local region as well
as global resolutions. This is often useful for running quick cases for testing, evaluating
specific vegetation types, or land-units, or running with observed data for a specific site.
There are three different ways to do this: PTS_MODE,
CLM_1PT_NAME, and CLM_USRDAT_NAME.
PTS_MODE -- to run for a single point
using global datasets. |
CLM_1PT_NAME -- to run for a supported single-point
or regional dataset. |
CLM_USRDAT_NAME -- to run using your own datasets (single-point
or regional). |
Note:
PTS_MODEonly works for a single point, while the other two options can also work for regional datasets as well.
PTS_MODE enables you to run the model using global datasets, but just picking a
single point from those datasets and operating on it. It can be a very quick way to do fast
simulations and get a quick turnaround.
To setup a PTS_MODE simulation you use the "-pts_lat" and "-pts_lon"
arguments to create_newcase to give the latitude and longitude of the point you want to
simulate for (the code will pick the point on the global grid nearest to the point you
give. Here's an example to setup a simulation for the nearest point at 2-degree resolution
to Boulder Colorado.
> cd scripts > create_newcase -case testPTS_MODE -res f19_g16 -compset I -mach bluefire \ -pts_lat 40.0 -pts_lon -105 |
Important: By default it sets up to run with
USE_MPISERIAL(in the env_builld.xml file) turned on, which allows you to run the model interactively. On some machines this mode is NOT supported and you may need to change it to FALSE before you are able to build.
| Warning |
|
Note: You can change the point you are simulating for at run-time by changing the values of
PTS_LATandPTS_LONin the env_run.xml file.