-
Notifications
You must be signed in to change notification settings - Fork 360
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adds notes about using mksurfdata_map
- Loading branch information
1 parent
3e6959e
commit ff40c9c
Showing
2 changed files
with
55 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -77,7 +77,11 @@ Using the above-mentioned settings: | |
The [FATES User's Guide section on namelist options](https://fates-users-guide.readthedocs.io/en/latest/user/Namelist-Options-and-Run-Time-Modes.html) | ||
provides guidance on enabling these different FATES run modes. | ||
|
||
## Generate land initial condition | ||
## Create land surface dataset | ||
|
||
A new surface dataset for ELM is generated using `mksurfdata_map` and the notes about it are available [here](surface_dataset.md) | ||
|
||
Initial ELM condition can be generated using `interpinic` and the notes about it are available [here](interpinic.md). | ||
|
||
Check failure on line 84 in components/elm/docs/user-guide/index.md GitHub Actions / linterMultiple consecutive blank lines
|
||
## Generate land initial condition | ||
|
||
Initial ELM condition can be generated using `interpinic` and the notes about it are available [here](interpinic.md). | ||
Check failure on line 87 in components/elm/docs/user-guide/index.md GitHub Actions / linterFiles should end with a single newline character
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# Creating an ELM surface dataset | ||
|
||
The notes describe the steps in creating an ELM surface dataset at 0.5x0.5 resolution for 1950 on Perlmutter. | ||
|
||
1. Load the appropriate modules. | ||
|
||
``` | ||
Check failure on line 7 in components/elm/docs/user-guide/surface_dataset.md GitHub Actions / linterFenced code blocks should have a language specified
|
||
cd <e3ms-dir> | ||
eval $(./cime/CIME/Tools/get_case_env) | ||
``` | ||
|
||
2. Compile `mksurfdata_map`. | ||
Check failure on line 12 in components/elm/docs/user-guide/surface_dataset.md GitHub Actions / linterOrdered list item prefix
|
||
|
||
``` | ||
cd components/elm/tools/mksurfdata_map/src/ | ||
make clean | ||
export USER_LDFLAGS="-L$NETCDF_DIR/lib -lnetcdf -lnetcdff -lnetcdf_intel" | ||
export USER_LDFLAGS=$USER_LDFLAGS" -L$HDF5_DIR/lib -lhdf5 -lhdf5_fortran -lhdf5_hl_intel -lhdf5hl_fortran_intel" | ||
USER_FC=ifort LIB_NETCDF="`nc-config --flibs`" INC_NETCDF="`nf-config --includedir`" make VERBOSE=1 | ||
``` | ||
|
||
3. Build the namelist. This steps assumes that the resolution for which the new surface dataset is being created is a supported resolution. | ||
If the surface dataset is being created for an unsupported resolution, 16 mapping files will have to be created to map the raw datasets | ||
onto this unsupported resolution. | ||
|
||
``` | ||
cd ../ | ||
RES=0.5x0.5 | ||
YR=1950 | ||
DIN_LOC_ROOT=/global/cfs/cdirs/e3sm/inputdata | ||
./mksurfdata.pl -res $RES -years $YR -d -dinlc $DIN_LOC_ROOT | ||
mv namelist namelist.$RES.$YR | ||
``` | ||
|
||
4. Run `mksurfdata_map` via an interactive job. | ||
|
||
``` | ||
salloc --nodes 1 --qos interactive --time 01:00:00 --constraint cpu --account e3sm | ||
RES=0.5x0.5 | ||
YR=1950 | ||
NAMELIST=namelist.$RES.$YR | ||
srun -n 1 ./mksurfdata_map < $NAMELIST | ||
``` |