>From: Clint Rowe <address@hidden>
>Organization: University of Nebraska-Lincoln
>Keywords: 200009131309.e8DD9sb12051 ldm-mcidas LDM PNG pnga2area pqact.conf
Clint,
>After I sent my message, I checked and found out that I'm not as lazy as
>I thought I was -- I had already made the necessary changes for McIDAS
>filing.
Will wonders never cease ;-)
>However, I'm still going to be lazy enough to ask for the
>GEMPAK entries.
Ah, its good to have the old Clint back :-)
I am including info Chiz and I sent under separate covers to one site.
I think that the combination of responses give a good overview of the
"issues". I will let you decide which explanation is more to your liking.
Chiz's response:
# UW Products except Mollweide IR and WV and Antarctic composite and floaters
decoded
# into GEMPAK file hierarchy
MCIDAS ^pnga2area Q1 (U[^ACXY1]) (.*) (.*)_IMG (0.65)um (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/\3/\5/VIS/VIS_\6_\7
MCIDAS ^pnga2area Q1 (U[^ACXY1]) (.*) (.*)_IMG (6.8)um (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/\3/\5/WV/WV_\6_\7
MCIDAS ^pnga2area Q1 (U[^ACXY1]) (.*) (.*)_IMG (10.7)um (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/\3/\5/IR/IR_\6_\7
# floater1
MCIDAS ^pnga2area Q1 (UA) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/\3_fl1/\5/\4/\4_\6_\7
# floater2
MCIDAS ^pnga2area Q1 (UC) (.*) (.*)_IMG (.*)um (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/\3_fl2/\5/\4/\4_\6_\7
# UW Antarctic composite decoded into GEMPAK hierarchy
MCIDAS ^pnga2area Q1 (U1) (.*) (.*)_IMG (.*) (.*) (........) (....)
PIPE -close
pnga2area -vl /usr/local/ldm/logs/ldm-mcidas.log
/data/ldm/gempak/images/sat/ANTARCTIC/\5/IR/IR_\6_\7
# CIMSS Cloud Top Pressure - McIDAS product code CA
MCIDAS ^pnga2area Q0 CA .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/CTP/CTP_\4_\5
# CIMSS Total Column Precipitable Water - McIDAS product code CB
MCIDAS ^pnga2area Q0 CB .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/PW/PW_\4_\5
# CIMSS Sea Surface Temperature - McIDAS product code CC
MCIDAS ^pnga2area Q0 CC .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/SST/SST_\4_\5
# CIMSS Lifted Index - McIDAS product code CD
MCIDAS ^pnga2area Q0 CD .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/LI/LI_\4_\5
# CIMSS CAPE - McIDAS product code CE
MCIDAS ^pnga2area Q0 CE .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/CAPE/CAPE_\4_\5
# CIMSS Ozone - McIDAS product code CF
MCIDAS ^pnga2area Q0 CF .... (.*) (.*) (.*) (........) (....)
PIPE -close
pnga2area /data/ldm/gempak/images/sat/SOUNDER/\3/OZONE/OZONE_\4_\5
My explanation:
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.
Tom
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.