TOVS Path-P IDL Tools Tutorial
Introduction |
Getting Started |
Tutorial:
1
2
3
4 |
Example:
1
2
3
4 |
Extended Help
Getting Started
These IDL tools have been written for use with IDL 6.0 or later and have been tested on Unix and Windows machines.
The IDL tools require that the TOVS Pathfinder Path-P Daily and Monthly Polar Gridded Atmospheric Parameters data files to be organized in a specific way on your disk. All the data files must be placed under the same base directory. The ancillary data files (tpp_n100_9999999_ancil.hdf for the Northern Hemisphere and tpp_s100_9999999_ancil.hdf for the Southern Hemisphere) must be in the base directory, while the daily data files must be in yearly subdirectories under the base directory. The directory name of each yearly subdirectory must be the 4-digit year. The easiest way to ensure that your directory is set up properly is to download the daily data tar files to the base directory and untar them from there. The yearly subdirectories will be created automatically.
Example:
- Unix systems: This example assumes that the data files will be stored in your home directory under a subdirectory named tovs, for example, in /usr/me/tovs (Note: This location is arbitrary; the data files can be stored anywhere in your file system that there is sufficient space). In this example, the ancillary data files (tpp_n100_9999999_ancil.hdf and tpp_s100_9999999_ancil.hdf) would be placed in /usr/me/tovs. The daily data files would be placed in the subdirectories /usr/me/tovs/1979 for 1979 data, /usr/me/tovs/1980 for 1980 data, and so on. One way of setting this up is to
download the daily data tar files to /usr/me/tovs and untar them from there to create the subdirectories automatically. Note: Files other than daily data files should not be put in the directories with the daily data files.
- Windows: This example assumes that the data files will be stored under the directory b:\tovs (Note: This location is arbitrary; the data files can be stored anywhere in your file system that there is sufficient space). In this example, the ancillary data files (tpp_n100_9999999_ancil.hdf and tpp_s100_9999999_ancil.hdf) would be placed in b:\tovs. The daily data files would be placed in the subdirectories b:\tovs\1979 for 1979 data, b:\tovs\1980 for 1980 data, and so on.
One way of setting up the correct directory structure is to download the tar files to b:\tovs and untar them from there to create the subdirectories automatically. Note: Files other than daily data files should not be put in the directories with the daily data files.
To download and run the tools from the TOVS Path-P FTP site, please perform the following steps. Implementation of each step will vary depending on your operating system and shell.
- Download tools from the TOVS Path-P FTP site
- Add the path to the tools to your IDL path
- Set the startup file
- Pick a fixed-width font for your output log
- Restart IDL
- Begin using the tools with the tutorial
- Download tools from the TOVS Path-P site
-
Unix systems: The exact syntax will depend on your
shell. This example assumes that you are putting the tools in a
directory named /usr/me/tovs/IDL_tools (Note: this location is arbitrary; the tools can be placed
anywhere in your file system). First change your current working
directory to the directory where the tools will reside. On systems using flavors of C shell, do this by typing the following at the command prompt:
> cd /usr/me/tovs/IDL_tools
Then connect to the TOVS Path-P FTP site by typing the following:
> ftp sidads.colorado.edu
Use 'anonymous' for the username and your e-mail address for the password. Once you have logged onto the FTP site, type the following command to navigate to the directory where the tools reside:
> cd pub/DATASETS/tovs/tools/IDL
Download all files by typing the following command:
> mget *.pro
Note:
You must download all the files to ensure that the tools will work properly.
- Windows: Create the directory that you are going to store
the tools in. Then use the FTP tool on your PC to download the
tools from the FTP directory pub/DATASETS/tovs/tools/IDL on
sidads.colorado.edu. An alternative method is to use a Web browser and go to ftp://sidads.colorado.edu/pub/DATASETS/tovs/tools/IDL/ to download the files.
Note:
You must download all the files to ensure that the tools will work properly.
- Add the path to the tools to your IDL path.
Note:
Be sure to add the new path without eliminating any existing paths.
- Unix systems: The exact syntax will depend on your
shell. On systems using flavors of C shell, an example of the command would be the following:
setenv IDL_PATH /usr/me/tovs/IDL_tools\:$IDL_PATH
Note: The pathname /usr/me/tovs/IDL_tools is only used as an example. If you get an error message similar to "IDL_PATH: undefined variable," you need to run the idl_setup script. If you do not know how to run this script, consult your system administrator.
- Windows: Start IDL and add the directory name where
you put the tools to the list of default paths using the
pull-down menus: File->Preferences->Path.
- Set the startup file.
There are two different version of the startup file. A Unix version called unixstrt.pro and a Windows version called winstrt.pro. When you use the startup file, IDL will compile each of the tool's programs in the correct order and will set the device visual so that the display colors behave correctly. The tools were built assuming that PseudoColor is used on Unix systems and decomposed color is turned off on Windows systems. Unexpected results will occur on the color displays if you run the tools using TrueColor. If you use a customized startup file, you may wish to merge the startup file provided with your own customizations.
- Unix systems: The exact syntax will
depend on your shell. On systems using flavors of C shell,
an example of the command would be the following:
setenv IDL_STARTUP /usr/me/tovs/IDL_tools/unixstrt.pro
Note: The pathname /usr/me/tovs/IDL_tools is only used as an example.
- Windows: Start IDL and change the startup file to the
full path name on your disk using the pull-down menus:
File->Preferences->Startup. For example, if you put the
tools in b:\tovs\IDL_tools, then you would enter
b:\tovs\IDL_tools\winstrt.pro.
- Pick a fixed-width font for your output log.
Some of the tools display text output in the IDL window. The output will be easier to read if you are using a fixed-width font such as Courier or Courier New.
- Unix systems: This will depend on the window manager
you are using. One way for users with xterm to do this is to
add the following line to your .Xdefaults file
xterm*font: -adobe-courier-*-o-*-*-20-*-*-*-*-*-*-*
- Windows: Start IDL and change the font for the
output log to Courier using the
pull-down menus: File->Preferences->Fonts. Select Output Log and then Courier font.
- Restart IDL.
For these changes to take affect, you must restart IDL. After restarting, your display should look similar to the following:
IDL Version 6.x. Research Systems, Inc.
Installation number: xxxx.
Licensed for use by: your company/institution
For basic information, enter "IDLInfo" at the IDL> prompt.
% Compiled module: COLORBAR.
% Compiled module: BLANK_LEGEND.
% Compiled module: MAKE_LEGEND.
% Compiled module: PAINT_LEGEND.
% Compiled module: SNOWICE_LEGEND.
% Compiled module: OCEAN_LEGEND.
% Compiled module: SSMI_CONVERT.
% Compiled module: SSMI_INVERSE.
% Compiled module: EASE_CONVERT.
% Compiled module: EASE_INVERSE.
% Compiled module: PPPU_ADD_SDS.
% Compiled module: PPPU_FILES.
% Compiled module: PPPU_GET_SDS_DESCRIPTIONS.
% Compiled module: PPPU_IS_ANCILLARY_SDS.
% Compiled module: PPPU_YYYYDOY_TO_JULDAY.
% Compiled module: PPP_READ.
% Compiled module: PPP_TOC.
% Compiled module: PPP_EXTRACT.
% Compiled module: PPP_STATS.
% Compiled module: PPP_PLATFORM.
% Compiled module: PPP_PLOT.
% Compiled module: PPP_PLOT_XPARAMS.
% Compiled module: PPP_COMPARE.
% Compiled module: PPP_SHOW.
% Compiled module: PPP_ANIMATE.
% Compiled module: PPP_SAVE.
% Compiled module: PPP_RESTORE.
% Compiled module: PLAY_GIF.
% Compiled module: PPP_PLATFORM
The Polar Pathfinder P-cube/TOVS IDL access routines are now installed.
Please refer to index.html in the HTML documentation,
for more information about these tools, including extended
help documentation.
Select Platform:
Enter 1 for P-cube
Enter 2 for TOVS Northern Hemisphere Path-P Daily
Enter 3 for TOVS Northern Hemisphere Path-P Monthly
Enter 4 for TOVS Southern Hemisphere Path-P Daily
:
The prompt at the end of the installation requires you to select the data you want to visualize. For this tutorial and data set, you will only be concerned with modes 2, 3, and 4 (P-cube is a different data set not discussed in this tutorial). Note: You can use the procedure ppp_platform at any time to switch data sets.
If you see compilation errors during startup, the first thing to check is if you have overwritten your current IDL_PATH (instead of appending the IDL tools directory to your existing path, thereby causing IDL to lose track of standard IDL functions). The way to check this is to print the value of IDL_PATH by printing the system variable !path and to confirm that the output looks similar to the following:
IDL> print, !path
/usr/me/tovs/IDL_tools:+/usr/local/rsi/idl5.1/idl_5.1/lib:+/usr/local/rsi/idl5.1/idl_5.1/examples
And not like this:
IDL> print, !path
/usr/me/tovs/IDL_tools
If you did overwrite your IDL_PATH, you must start a new window to get the original path back before re-executing the setenv commands above.
- Begin using the tools with the tutorial.
Please refer to the Extended Help documentation and the
Tutorial for examples and suggestions on how to run the tools.