LDT 7.2 Users’ Guide - NASA
Land Data ToolkitLDT 7.2 Users’ GuideMay 6, 2017Revision 1.4History:Revision1.4Summary of ChangesLDT 7.2 Public ReleaseNational Aeronautics and Space AdministrationGoddard Space Flight CenterGreenbelt, Maryland 207711DateMay 6, 2017
History:Revision1.31.21.11.0Summary of ChangesLDT 7.1 Public Release patch 3LDT 7.1 Public Release patch 1LDT 7.1 Public ReleaseLDT 7.1 Initial Release2DateNovember 7, 2016October 22, 2015April 27, 2015April 9, 2015
Contents1 Introduction1.17What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.1.1Version 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . .71.1.2Version 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . .71.1.3Version 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . .82 Background92.1LDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.2Summary of key features . . . . . . . . . . . . . . . . . . . . . . .93 Preliminary Information114 Obtaining the Source Code124.1Important Note Regarding File Systems . . . . . . . . . . . . . .124.2Public Release Source Code Tar File . . . . . . . . . . . . . . . .124.3Checking Out the Source Code . . . . . . . . . . . . . . . . . . .135 Building the Executable145.1Development Tools . . . . . . . . . . . . . . . . . . . . . . . . . .145.2Required Software Libraries . . . . . . . . . . . . . . . . . . . . .145.3Optional Software Libraries . . . . . . . . . . . . . . . . . . . . .165.4Build Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .175.5Generating documentation . . . . . . . . . . . . . . . . . . . . . .193
6 Running the Executable207 LDT Config File217.1Overall driver options . . . . . . . . . . . . . . . . . . . . . . . .217.2Domain specification . . . . . . . . . . . . . . . . . . . . . . . . .337.2.1Cylindrical lat/lon . . . . . . . . . . . . . . . . . . . . . .337.2.2Lambert conformal . . . . . . . . . . . . . . . . . . . . . .347.2.3Gaussian . . . . . . . . . . . . . . . . . . . . . . . . . . .347.2.4Polar stereographic . . . . . . . . . . . . . . . . . . . . . .347.2.5HRAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357.2.6Mercator . . . . . . . . . . . . . . . . . . . . . . . . . . .357.3Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357.4Crop-Irrigation Parameters . . . . . . . . . . . . . . . . . . . . .417.5Soil Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .457.6Topography Parameters . . . . . . . . . . . . . . . . . . . . . . .517.7LSM-specific Parameters . . . . . . . . . . . . . . . . . . . . . . .557.7.1WRSI model parameter files . . . . . . . . . . . . . . . . .767.8Climate Parameters . . . . . . . . . . . . . . . . . . . . . . . . .767.9Forcing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .787.9.1NLDAS-2 Forcing based parameter inputs . . . . . . . . .787.9.2NLDAS-1 Forcing based parameter inputs . . . . . . . . .787.9.3PRINCETON Forcing based parameter inputs . . . . . .797.9.4NAM242 Forcing based parameter inputs . . . . . . . . .797.9.5GDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .794
7.9.6ECMWF . . . . . . . . . . . . . . . . . . . . . . . . . . .807.9.7ECMWF Reanalysis Forcing based parameter inputs . . .817.9.8MERRA-2 Forcing based parameter inputs . . . . . . . .827.9.9TRMM 3B42RTV7 precipitation . . . . . . . . . . . . . .827.9.10 TRMM 3B42V6 precipitation . . . . . . . . . . . . . . . .827.9.11 TRMM 3B42V7 precipitation . . . . . . . . . . . . . . . .827.9.12 CMAP precipitation . . . . . . . . . . . . . . . . . . . . .827.9.13 CMORPH precipitation . . . . . . . . . . . . . . . . . . .837.9.14 MERRA-Land forcing . . . . . . . . . . . . . . . . . . . .837.9.15 MERRA2 forcing . . . . . . . . . . . . . . . . . . . . . . .837.9.16 RDHM356 forcing . . . . . . . . . . . . . . . . . . . . . .837.9.17 RFE2Daily precipitation . . . . . . . . . . . . . . . . . . .837.9.18 RFE2gdas precipitation . . . . . . . . . . . . . . . . . . .837.9.19 CHIRPSv2 precipitation . . . . . . . . . . . . . . . . . . .837.9.20 Stage II precipitation . . . . . . . . . . . . . . . . . . . .847.9.21 Stage IV precipitation . . . . . . . . . . . . . . . . . . . .847.9.22 GEOS5 forecast. . . . . . . . . . . . . . . . . . . . . . .847.9.23 GFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .847.10 LIS restart preprocessing options . . . . . . . . . . . . . . . . . .847.11 Ensemble restart model options . . . . . . . . . . . . . . . . . . .857.12 NUWRF preprocessing for real options . . . . . . . . . . . . . . .867.13 Data Assimilation preprocessing options . . . . . . . . . . . . . .867.14 Artificial neural networks . . . . . . . . . . . . . . . . . . . . . . 1025
7.14.1 GHCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037.14.2 LIS soil moisture output . . . . . . . . . . . . . . . . . . . 1037.14.3 MOD10A1 . . . . . . . . . . . . . . . . . . . . . . . . . . 1057.14.4 MODIS LST . . . . . . . . . . . . . . . . . . . . . . . . . 105A Description of output files from LDT106A.0.1 Dimensions attributes . . . . . . . . . . . . . . . . . . . . 106A.0.2 Variable attributes . . . . . . . . . . . . . . . . . . . . . . 107B Cylindrical Lat/Lon Domain Example108C Lambert Conformal Domain Example113D Gaussian Domain Example114E Polar Stereographic Domain Example136F HRAP Domain Example137G Mercator Domain Example1386
1IntroductionThis is the User’s Guide for the Land surface Data Toolkit (LDT). This document describes how to download and install the LDT software and instructionson building an executable.This document consists of several sections, described as follows:1 Introduction: the section you are currently reading2 Background: general information about the LDT3 Preliminary Information: general information, steps, instructions, anddefinitions used throughout the rest of this document4 Obtaining the Source Code: the steps needed to download the sourcecode5 Building the Executable: the steps needed to build the LDT executable1.11.1.1What’s NewVersion 7.21. Includes artificial neural network processing runmode1.1.2Version 7.11. Includes MetTimeDScale runmode2. Includes Metforcproc runmode3. Supports crop parameters4. Supports CLM2 parameters5. Supports Flake parameters6. Supports Mosaic parameters7. Supports Noah parameters8. Supports SiB2 parameters9. Supports VIC parameters7
10. Supports TRMM 3B42 V7 real time precipitation11. Supports Aquarius L2 soil moisture observations12. Supports GCOMW AMSR2 L3 soil moisture observations13. Supports SMOS L2 soil moisture observations14. Supports simulated GRACE products1.1.3Version 7.01. This is the initial version developed for processing data inputs to LISversion 7.0 or higher.8
2BackgroundA key step in preparing for land surface model (LSM) and hydrologic modelsimulations is ensuring that all parameters and data inputs belong to the samegrid, projection, units, etc. The Land surface Data Toolkit (LDT) is an integrated framework designed specifically for processing data inputs for such landsurface and hydrological models. The system not only acts as a pre-processor tothe NASA Land Information System (LIS), which is an integrated frameworkdesigned for multi-model LSM simulations and data assimilation (DA) integrations, but as a land surface-based observation and DA input processor. LDTis also capable of deriving restart inputs and ensuring data quality control forinputs to LSMs and DA routines.2.1LDTLDT provides an environment for processing LSM data and parameters, restartfiles and data assimilation based inputs (e.g., for bias correction methods). LDToffers and will offer a variety of user options and inputs to processing datasetsfor use within LIS and even stand-alone models. LDT is being designed withnot only LIS in mind but for other independent models and data processingsystems as well. This intended design is facilitated by the use of common dataformats, like NetCDF, which provide detailed data header information.LDT shares similar object oriented framework designs as LIS, with a numberof points of flexibility known as “plugins”. Specific implementations are addedto the framework through the plugin-interfaces. LDT uses the plugin-basedarchitecture to support the processing of different types of observational datasets, ranging from in-situ, satellite and remotely sensed and reanalysis products.2.2Summary of key featuresThe key capabilities of LDT can be summarized as follows: Processing and grouping parameters needed for different LSMs and hydrologic models Producing observation-based data assimilation inputs (e.g., CDF matching) Generate custom-made restart files for LSMs Read in a variety of model inputs, for example:9
– Land cover maps — UMD AVHRR, MODIS-IGBP, USGS, etc.– Soil parameters — soil fractions, texture, color, etc.– Topographic — elevation, slope, aspect, etc.– Dynamic parameters — greenness fraction, LAI/SAI, albedo, etc. Expanding LSM parameter tiling options to include topographic, soils,and other parameter information, beyond just land cover type tiling Options for reading in or deriving a land/water mask during processing10
3Preliminary InformationThis section provides some preliminary information to make reading this guideeasier.Commands are written with a fixed-width font. E.g.:% cd /path/to/LDT% ls“. . . compiler flags, then run gmake.”NOTE: The ‘%’ symbol represents the command-line prompt. You do not typethat when entering any of the commands.File names are written in italics. E.g.:/path/to/LDT/src11
4Obtaining the Source CodeThis section describes how to obtain the source code needed to build the LDTexecutable.Beginning with LIS public release 7.1rp1, the LIS and LDT source code isavailable as open source under the NASA Open Source Agreement (NOSA).Please see LIS’ web-site for a copy the NOSA.Due to the history of LDT’s development, prior versions of the LDT source codemay not be freely distributed. That older source code is available only to U.S.government agencies or entities with a U.S. government grant/contract. LIS‘’web-site explains how qualified persons may request a copy of the older sourcecode.4.1Important Note Regarding File SystemsLDT is developed on Linux/Unix platforms. Its build process expects a casesensitive file system. Please make sure that you unpack and/or ‘svn checkout‘the LDT code into a directory within a case sensitive file system. In particular, ifyou are using LDT within a Linux-based virtual machine hosted on a Windowsor Macintosh system, do not compile/run LDT from within a shared folder.Move the LDT source code into a directory within the virtual machine.4.2Public Release Source Code Tar FileThe LDT 7.2 source code is available for download as a tar-file from LIS’ website. All users are encouraged to fill in the Registration Form and join themailing list, both also accessible from LIS’ web-site. After downloading theLDT tar-file:1. Create a directory to unpack the tar-file into. Let’s call it TOPLEVELDIR.2. Place the tar-file in this directory.% mv LDT public release 7.2r.tar.gz TOPLEVELDIR3. Go into this directory.% cd TOPLEVELDIR4. Run gzip -dc LDT public release 7.2r.tar.gz tar xf This command will unzip and untar the tar-file.12
Note that the directory containing the LDT source code will be referred to as WORKING throughout the rest of this document.4.3Checking Out the Source CodeThe source code is maintained in a Subversion repository. Only developers mayhave access to the repository. Developers must use the Subversion client (svn)to obtain the LDT source code. If you need any help regarding Subversion,please go to http://subversion.apache.org/.Developers must first obtain access to the LDT source code respository. Toobtain access you must contact the LDT team. Once you have access to therepository, you will be given the correct Subversion command to run to checkoutthe source code.1. Create a directory to checkout the code into. Let’s call it TOPLEVELDIR.2. Go into this directory.% cd TOPLEVELDIR3. Check out the source code into a directory called src.For the public version, run the following command:% svn checkout /public7.2srcNote that the directory containing the LDT source code will be referred to as WORKING throughout the rest of this document.Source code documentation may be found on LDT’s web-site. Follow the “Documentation” link.13
5Building the ExecutableThis section describes how to build the source code and create LDT’executable: named LDT.5.1Development ToolsThis code has been compiled and run on Linux PC (Intel/AMD based) systemsand Cray systems. These instructions expect that you are using such a system.In particular you need: Linux– Compilers either Intel Fortran Compiler versions 14 or 15 with corresponding Intel C Compiler or GNU’s Compiler Collection 4.9.2, both gfortran and gcc– GNU’s make, gmake, version 3.77 or 3.81– perl, version 5.10 Cray/Linux– either Intel Fortran Compiler versions 14 or 15 with correspondingIntel C Compiler– GNU’s make, gmake, version 3.77 or 3.81– perl, version 5.105.2Required Software LibrariesIn order to build the LDT executable, the following libraries must be installedon your system: Earth System Modeling Framework (ESMF) version 5.2.0rp3 (or ad/releases.shtml)Note that starting with ESMF version 5, the ESMF development team istrying to maintain backwards compatibility with its subsequent releases.The LDT development team, however, has neither compiled nor testedagainst versions of ESMF newer than 5.2.0rp3.14
JasPer version 1.900.1.(http://www.ece.uvic.ca/ frodo/jasper/).Note that when running the configure command you must include the--enable-shared option. GRIB-API version 1.12.3 (or RIB/Home) NetCDF either version 3.6.3 or version 4.3.0 (or df/)Please read the on-line documentation for details on installing NetCDF.Addtional notes for NetCDF 4:– You must also choose whether to compile with compression enabled.Compiling with compression enabled requires HDF 5 and zlib libraries. To enable compression, add --enable-netcdf-4 to theconfigure options. To disable compression, add --disable-netcdf-4to the configure options.An example of installing NetCDF 4 without compression:% ./configure --prefix HOME/local/netcdf-4.3.0 --disable-netcdf-4% gmake% gmake installAn example of installing NetCDF 4 with compression:% CPPFLAGS -I HOME/local/hdf5/1.8.11/include \ LDFLAGS -L HOME/local/hdf5/1.8.11/lib \ ./configure --prefix HOME/local/netcdf/4.3.0 --enable-netcdf-4% gmake% gmake install– You must also download the netcdf-fortran-4.2.tar.gz file. First install the NetCDF C library, then install the NetCDF Fortran library.Again, please read the on-line documentation for more details.An example of installing the NetCDF 4 Fortran library:% LD LIBRARY PATH HOME/local/netcdf/4.3.0/lib: LD LIBRARY PATH \ CPPFLAGS -I HOME/local/netcdf/4.3.0/include \ LDFLAGS -L HOME/local/netcdf/4.3.0/lib \ ./configure --prefix HOME/local/netcdf/4.3.0% gmake% gmake install15
5.3Optional Software LibrariesThe following libraries are not required to compile LDT. They are used to extendthe functionality of LDT. HDFYou may choose either HDF version 4, HDF version 5, or both.HDF is used to support a number of remote sensing datasets.If you wish to use MODIS snow cover area observations or NASA AMSR-Esoil moisture observations, then you need HDF 4 support.If you wish to use ANSA snow cover fraction observations, then you needHDF 5 support.If you wish to use PMW snow observations, then you need both HDF 4and HDF 5 support.– HDF 4If you choose to have HDF version 4 support, please download theHDF source for version 4.2r4 (or later) from (http://www.hdfgroup.org/products/hdf4)and compile the source to generate the HDF library. Make sure thatyou configure the build process to include the Fortran interfaces byadding the --enable-fortran option to the configure command.Note that HDF4 contains its own embedded version of NetCDF. Youmust disable this support by adding the --disable-netcdf optionto the configure command.Note that when compiling LDT with HDF 4 support, you must alsodownload and compile HDF-EOS2 (http://hdfeos.org/).– HDF 5If you choose to have HDF version 5 support, please download theHDF source for version 1.8.11 (or later) from (http://www.hdfgroup.org/HDF5/)and compile the source to generate the HDF library. Make sure thatyou configure the build process to include the Fortran interfaces byadding the --enable-fortran option to the configure command.To install these libraries, follow the instructions provided at the various URLlisted above. These optional libraries have their own dependencies, which shouldbe documented in their respective documentation.Note that due to the mix of programing languages (Fortran and C) used byLDT, you may run into linking errors when building the LDT executable. Thisis often due to (1) the Fortran compiler and the C compiler using different cases(upper case vs. lower case) for external names, and (2) the Fortran compilerand C compiler using a different number of underscores for external names.16
When compiling code using Absoft’s Pro Fortran SDK, set the following compiler options:-YEXT NAMES LCS -s -YEXT SFX -YCFRL 1These must be set for each of the above libraries.5.4Build Instructions1. Perform the steps described in Section 4 to obtain the source code.2. Goto the WORKING directory. This directory contains two scripts forbuilding the LDT executable: configure and compile.3. Set the LDT ARCH environment variable based on the system you areusing. The following commands are written using Bash shell syntax. For an AIX system% export LDT ARCH AIX For a Linux system with the Intel Fortran compiler% export LDT ARCH linux ifc For a Linux system with the Absoft Fortran compiler% export LDT ARCH linux absoft For a Linux system with the Lahey Fortran compiler% export LDT ARCH linux lf95It is suggested that you place this command in your .profile (or equivalent)startup file.4. Run the configure script first by typing:% ./configureThis script will prompt the user with a series of questions regarding support to compile into LDT, requiring the user to specify the locations ofthe required and optional libraries via several LDT specific environmentvariables. The following environment variables are used by LDT.17
VariableLDT FCLDT CCLDT MODESMFLDT LIBESMFLDT JASPERLDT GRIBAPILDT NETCDFLDT HDF4LDT HDF5LDT HDFEOSDescriptionFortran 90 compilerC compilerpath to ESMF module filespath to ESMF library filespath to JasPer librarypath to GRIB-API librarypath to NetCDF librarypath to HDF4 librarypath to HDF5 librarypath to HDFEOS edrequiredrequiredoptionaloptionaloptionalNote that the CC variable must be set to a C compiler, not a C compiler.A C compiler may mangle internal names in a manner that is notconsistent with the Fortran compiler. This will cause errors during linking.It is suggested that you add these definitions to your .profile (or equivalent)startup file.You may encounter errors either when trying to compile LDT or whentrying to run LDT because the compiler or operating system cannotfind these libraries. To fix this, you must add these libraries to your LD LIBRARY PATH environment variable. For example, say that you areusing ESMF, GRIB-API, NetCDF, and HDF5. Then you must executethe following command (written using Bash shell syntax):% export LD LIBRARY PATH LDT HDF5/lib: LDT LIBESMF: LDT NETCDF/lib: LDT GRIBAPI/lib: LD LIBRARY PATHIt is also suggested that you add this command to your .profile (or equivalent) startup file.5. An example execution of the configure script is shown below:% --------------------------------Setti
In particular you need: Linux { Compilers either Intel Fortran Compiler versions 14 or 15 with correspond-ing Intel C Compiler or GNU’s Compiler Collection 4.9.2, both gfortran and gcc { GNU’s make, gmake, version 3.77 or 3.81 { perl, version 5.10 Cray/Linux { either Intel Fortran Compiler versions 14 or 15 with corresponding Intel C Compiler
LEV LDT/SUV 2002 Chevrolet S10 Pickup 57,690 4 cylinder LEV LDT/SUV 2002 Chrysler Grand Cherokee 83,200 8 cylinder LEV LDT/SUV 2003 Toyota Tacoma 100,535 4 cylinder LEV LDT/SUV 2003 Nissan Pathfinder 110,055 6 cylinder
Spreadsheets (.xls, .xlsx). After locating the ldt file, the project setup will read the given file and allow you to locate the position of the attributes corresponding to the columns in your LDT. Then, you will choose which column includ
the new ldt entries, because the array is allocated through the vmalloc() allocator for each process that writes LDT entries using the modify_ldt(2) system call. -We are going to add one with a magic HEX value that is in kernel space, and then we are going to scan using signals and “verr” syscall for a
Windows supports setting up custom LDT entries o used on a per-process basis o 32-bit only (x86-64 has limited segmentation support) Only code / data segments are allowed. The entries undergo thorough sanitization before reaching LDT. o Otherwise, user could install
was not enthusiasm and enjoyment in achieving, then little was gained. Enjoyment from sport was a most important aspect for young athletes. NomineesJor 1990 Sportspenon 91the Year -Back row (ldt to right), Mark lames, Nadine Watson, lane Nixon, Rachel Long. Front "'w (ldt to right), Peter W
2009) and from the LDT (VaLex) (McGillivray, 2013). Latin Vallex is a recently created lexical resource for Latin consisting in a semantic-based valency lexicon built in conjunction with the se-mantic and pragmatic annotation of the IT-TB and the LDT (Passarotti et al.,2016). Presently, Latin Valle
The domestic automobile industry is a large, mature industry, but its size is expected to increase as foreign producers locate additional production facilities in the United States, and the LDT market continues to remain strong. In 1998 and 1999, the automobile and LDT assembly industry was comprised of 66 establishments, which are owned by 14 .
propose a new tool namely, ASK-LDT 2.0, which is a web-based graphical authoring tool that fully supports the (a) process of authoring LDs by utilizing the main IMS LD elements, as well as (b) the process of importing and exporting LDs in IMS LD compatible format. Table 1. Comparison of Existing LD Authoring Tools
