Date: Thu, 28 Mar 2024 16:27:10 -0400 (EDT) Message-ID: <752805965.1649.1711657630346@gs-ed-prod-wiki1.earthdata.nasa.gov> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1648_47024502.1711657630346" ------=_Part_1648_47024502.1711657630346 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Q: I have thousands of =
HDF-EOS data sets I want to use with HEG. It's too time-consuming to use th=
e GUI one at a time. What can I do?
A: You can stack many runs on the GUI's Accepted List, but for more than 5-1=
0 runs, it's still cumbersome to open files and load up options. What you n=
eed is to run HEG on the "Commmand Line". There are quite a few users who d=
o this and they almost always need some guidance getting started.Q: What do I need to start running on=
the "Command Line"?
A: You need 3 th=
ings to get started (trying to keep things simple for now):
a) You'll need to know which executable to use in your bin directory. (i.e.= "swtif" for SWATH data sets, "resample" for GRID data sets.)
b) You'll need to create a parameter file. This is a ascii text file that i= s read by the executable and contains the instructions and options for HEG = executable to perform.
c) You'll need to set the ENVIRONMENT VARIABLES.
Then, you can execute a command line string such as the following to run= the instructions in the parameter file:
> swtif -p "parameter_file_name"
Q: How does this run the=
thousands of HDF-EOS data sets?
A: T=
he parameter file can stack up thousands of runs. Each run is a block of te=
xt with a BEGIN and END part.
Q: =
How do I make a parameter file?
A: =
span>Instructions are in the HEG User's Guide, but a much easier way is to =
load one data set into the GUI, set your options (i.e output format, type o=
f reprojection, field to work on, etc). Once your run is on the "Accepted L=
ist", then stack another another run in the "Accepted List". Then "save" it=
. This will save the parameter file. You'll be asked where to save it. Use =
this parameter file as a "TEMPLATE". There are simple fields such as input =
filename, output filename, output projection type, etc. Note how you've sav=
ed more than one run. Because of this, you'll see how more than one run can=
be inside a parameter file (i.e. NUM_RUN =3D 2 on the top line).Q: Is there another way of running batch=
job for processing thousands of HDF-EOS data sets?Yes. You may also use an script for the HEG job for processin=
g a bunch of similar files on Command line.
A:<=
span>
Q: The parameter file has the extents (corner points) of t=
he input data set. How can I know what these are?
A:
Set your ENVIRONMENT VARIABLES, then run it as such:
hegtool -h "name_of_data_set"
This will create an output file called HegHdr.hdr*. It will contain info=
rmation about the HDF-EOS data set. This is what's used to load the informa=
tion you see on the GUI. It will contain corner point extents, pixel resolu=
tion, etc.
Q: What a=
re the ENVIRONMENT VARIABLES that need to be set?
A:
MRTDATADIR=3D/home/bob/HEG/data
PGSHOME=3D/home/bob/HEG/TOOLKIT_MTD
Windows user's will need an extra one:
MRTBINDIR=3Dc:\cygwin\home\bob\HEG\bin
Q: Can I run HEG oin the Command L=
ine mode in Windows (cmd window)?
A: =
Yes, but generally Windows users (who don't relate well to command line usa=
ge) find it difficult. Only one person I know has tried this. Ask me if you=
really want to know.
Q: I'm a =
Unix user and want to run on Windows. Is there an easier way?
A:=
Yes. Download Cygwin and this will simulate the=
Unix environment. There are still *.exe files to run, but Cygwin handles t=
his.