[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20000913: Configuring pqact.conf to file PNG images for GEMPAK/GARP/NMAP
- Subject: 20000913: Configuring pqact.conf to file PNG images for GEMPAK/GARP/NMAP
- Date: Wed, 13 Sep 2000 14:01:19 -0600
>From: address@hidden (Chris Hennon)
>Organization: Ohio State
>Keywords: 200009111601.e8BG1gb11030 LDM pqact.conf GEMPAK GARP NMAP
Chris,
>OK - I made the change and I'm getting the imagery.
Progress. I like it.
>So I guess now my
>only question refers to the data structure itself. What does one have to
>do in order to have the same directory structure for satellite images
>(i.e. GOES-8/4km/IR/) that was produced from the gempak script nsat_links?
This is very easy. You have to have specific pqact.conf entries for
each kind of product. The reason is that there is nothing in the satellite
information that will lead to a directory element called 'IR', 'VIS',
'WV', etc.
The header of the products in the broadcast can be used to create your
directory structure, or you can use pnga2area syntax to do it directory.
>In my current configuration, the images are parsed only by resolution.
The header has a number of pieces of information that you will likely
want to take advantage of. Let's use the GOES-8, 4 km, IR image
as an example. I don't know the particulars of the directory structure
you use for GEMPAK/GARP/NMAP, but I assume that they are something
like
/usr/local/ldm/data/gempak/images
/ / | \
GOES-8 GOES-10 GOES-8_fl1 GOES-8_fl2 ANTARCTIC ...
/ \ / \
4km 8km 4km 8km
/ \ \
VIS IR WV
etc.
The pqact.conf entries that will populate the GOES-8 portion of this tree
would be:
# Example headers from PNG compressed, UW broadcast images (taken from
# a 'notifyme -vxl- -f MCIDAS -o 3600 -h twister.sbs.ohio-state.edu'
#
# pnga2area Q1 UI 153 GOES-8_IMG 10.7um 4km 20000913 1915
# pnga2area Q1 UV 143 GOES-8_IMG 0.65um 4km 20000913 1915
# pnga2area Q1 UW 213 GOES-8_IMG 6.8um 8km 20000913 1915
# UW GOES-8 'IR' (10.7 um) product decoded into GEMPAK directory/name hierarchy
MCIDAS ^pnga2area Q1 (UI) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close /usr/local/ldm/decoders/pnga2area
-a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT
-b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND
/usr/local/ldm/data/gempak/images/\3/\5/IR/IR_\6_\7
This will result in files like:
/usr/local/ldm/data/gempak/images/GOES-8/4km/IR/IR_20000913_1915
A corresponding entry for GOES-8 'VIS' (0.65 um) images would be:
MCIDAS ^pnga2area Q1 (UV) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close /usr/local/ldm/decoders/pnga2area
-a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT
-b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND
/usr/local/ldm/data/gempak/images/\3/\5/VIS/VIS_\6_\7
This will result in files like:
/usr/local/ldm/data/gempak/images/GOES-8/4km/VIS/VIS_20000913_1915
GOES-8 'WV' (6.8 um) images would be filed by:
MCIDAS ^pnga2area Q1 (UW) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close /usr/local/ldm/decoders/pnga2area
-a /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATANNOT
-b /usr/local/ldm/ldm-mcidas-7.6.3/etc/SATBAND
/usr/local/ldm/data/gempak/images/\3/\5/WV/WV_\6_\7
This will result in files like:
/usr/local/ldm/data/gempak/images/GOES-8/8km/WV/WV_20000913_1915
You can see that the only thing changing here is the image product
codes (UI, UV, and UW) and the "hardwired" directory names (IR, VIS,
WV).
The mapping of product codes to platform/sensor for Unidata-Wisconsin
datastream products is (GOES-East is GOES-8; GOES-West is GOES-10):
pcode platform/sensor wavelength
-------+---------------------------+-------------
U1 Antarctic IR Composite 10.7 um (nominal)
U3 Manually Digitized Radar (N/A)
U5 GOES-West US IR Band 4 10.7 um
U9 GOES-West US Visible 0.65 um
UA Educational Floater I (variable)
UB GOES-West US Water Vapor 6.8 um
UC Educational Floater II (variable)
UI GOES-East US IR Band 4 10.7 um
UR Research Floater (inactive)
UV GOES-East US Visible 0.65 um
UW GOES-East US Water Vapor 6.8 um
UX Mollweide Composite IR 10.7 um (nominal)
UY Mollweide Composite H2O 6.8 um
So, you will need a separate entry for each product you want to file
directly for GEMPAK/GARP/NMAP _IF_ you want to keep with the 'IR', 'VIS',
and 'WV' designators.
If you don't mind switching to use of the image wavelengths directly,
you can condense your pqact.conf entries. For example, yere is what we
use on a machine we manage here at UCAR (NOTE: GEMPAK/GARP/NMAP do not
support display for the Mollweide and MDR products):
# UW products except Mollweide IR and WV and Antarctic composite and floaters
# decoded into GEMPAK directory/name hierarchy
MCIDAS ^pnga2area Q1 (U[^ACXY13]) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/\3/\5/\4/\4_\6_\7
# Educational Floater-I
MCIDAS ^pnga2area Q1 (UA) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/\3_fl1/\5/\4/\4_\6_\7
# Educational Floater-II
MCIDAS ^pnga2area Q1 (UC) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/\3_fl2/\5/\4/\4_\6_\7
# Mollweide Global IR
MCIDAS ^pnga2area Q1 (UX) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/MOLL-IR/56km/\4/\4_\6_\7
# Mollweide Global Water Vapor
MCIDAS ^pnga2area Q1 (UY) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/MOLL-WV/56km/\4/\4_\6_\7
# Antarctic Composite IR
MCIDAS ^pnga2area Q1 (U1) (.*) (.*)_IMG (.*) (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/ANTARCTIC/\5/10.7/10.7_\6_\7
# Manually Digitized Radar
MCIDAS ^pnga2area Q1 (U3) (.*) (.*) (.*) (.*) (........) (....)
PIPE -close
util/pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/nport/MDR/\5/MDR/MDR_\6_\7
Your directory structure will change if you adopt this, and you will
have to reconfigure GARP to understand the change.
>Thanks.
I hope that this helped.
Tom