[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020305: hosting ADDE access to Unidata NEXRAD composite imagery (cont.)



>From: "Thomas L. Mote" <address@hidden>
>Organization: University of Georgia
>Keywords: 200203051400.g25E0BK05321 McIDAS ADDE NEXRAD composite

Tom,

>It looks like we are stable again. For some reason, many of the LINUX 
>systems on our campus apparently were lost from the network about 1a.m. 
>Saturday. Most systems have an "updateme" script provided by the 
>university for patches, security updates, etc. I saw that running when 
>I went to restart the networking and suspect that must have created the 
>problem. The NOAAPort system had then become backed up as the data 
>buffer filled and needed some attention. Anyway, it all seems to be 
>fine now.

Sounds good.

>I have not been receiving the FNEXRAD feed. Other than the products you 
>are injecting into the data stream, is there anything else on FNEXRAD 
>that I cannot get on NOAAPort?

FNEXRAD consists of three floater NEXRAD site's products (you are
getting these by NOAAPORT) and several NEXRAD composites we are
creating on motherlode here in Boulder:

o 1 km N0R floater composite both as a grib message and as an image in
  PNG compressed AREA format
o 6 km N0R national compoiste both as a grib message and as an image in
  PNG compressed AREA format
o 10 km RCM national composite as an image in PNG compressed AREA format

The grib message that the RCM image is created from is on NOAAPORT in
the NWS TG (channel 3).

>In other words, can we set it up so that we are only requesting 
>products on the FNEXRAD feed that are not available from NOAAPort? 

Yes, absolutely.  In addition to the image products in FNEXRAD, there
is one image, the 1 km N0R national composite, in the NIMAGE feed.  All
of the other products in the NIMAGE feed come from NOAAPORT channels 1
and 2.

>Let me know... Tom

Here are the request lines that limit ingest to just the images that
I am setting up as an ADDE dataset named NEXRCOMP:

request NIMAGE  "^rad_" atm.geo.nsf.gov
request FNEXRAD "^pnga2area Q5" atm.geo.nsf.gov

Here is more complete list of the products to be served:

Product                    Decoded file size  Frequency    Feed
--------------------------+------------------+------------+--------
10 km national RCM           166880 bytes     30      min  FNEXRAD
1 km regional floater N0R    361280 bytes     7 - 10  min  FNEXRAD
6 km national N0R            401280 bytes     7 - 10  min  FNEXRAD
1 km national N0R          14208533 bytes     10 - 15 min  NIMAGE

The size of the files as they are broadcast are modest for the smaller
composites, and are up to about 1 MB for the 1 km national N0R
composite.  The exact size of each depends on how much weather is
active across the country.

Comments:

At the upcoming User's Committee meeting, we will be seeking guidance
on whether or not to:

o replace the MDR product in the Unidata-Wisconsin feed (LDM feed type
  MCIDAS) with the 6 km national N0R composite (or simply drop the MDR
  product altogether)

o drop the generation of the floater since sites will be able to
  use the national 1 km composite to create their own sectors

o figure out if continued generation of an image from the RCM composite
  grib is needed by any site.  This product is the one most like, but
  vastly superior to, the MDR product in the UW stream.

o whether or not to move the 1 km composite from the NIMAGE feed to
  a different one (like the FNEXRAD or MCIDAS feeds)

The user committee meeting is scheduled for March 14 & 15.

So, you may well decide to wait until the potential juggling of
feeds/products is complete before taking any action.  I have been
setting up other ADDE servers for display of all of the products so we
can get user feedback before committing to any moves.

If you do decided to go ahead and setup ingestion and decoding of the
images, I can provide you with the pqact.conf actions that will be
needed and the procedure for setting up the ADDE dataset.  My offer to
do this for you (in a previous email) still stands.  In addition to the
LDM mods, I would need to make sure that your McIDAS installation is up
to current addendum levels (plus one that has not been released yet).
Of course, I can coach you through all of the necessary steps so that
you will be familiar with the upgrade/setup procedure.

If you want me to to setup the LDM and ADDE sides, I would also take
the opportunity to turn on ADDE logging and rotation of those log
files.  The log files would be put into the ~ldm/logs directory and
rotated with the LDM newlog facility.  The idea behind turning on ADDE
logging would be so that you could monitor who is accessing your
machine by ADDE and how much data they are transferring.  For
reference, the simple output of logging (the listing routine has
several different modes) looks like (list taken from motherlode):

<login as 'mcidas'>
cd workdata
addeinfo.k
ADDEINFO: Start
ADDE Cumulative Totals: 2002061.070347 - 2002064.152717
IP                Bytes Sent  Client Name
-----------------+-----------+--------------------------------
192.203.136.227     4.03D+08  climate.cod.edu
155.42.21.3         2.24D+07  cirrus.lsc.vsc.edu
192.149.107.23      7.28D+08  psnldm.nsbf.nasa.gov
198.120.3.120       4.52D+08  wxmcidas.nsbf.nasa.gov
146.7.97.225        6.28D+08  cirrus.smsu.edu
210.219.35.131      3.90D+05  metri1.metri.re.kr
131.156.8.47        3.62D+08  weather.admin.niu.edu
128.95.89.44        7.77D+05  air89.atmos.washington.edu
140.172.240.32      7.43D+04  cumulus.al.noaa.gov
65.58.56.61         1.95D+06  dialup-65.58.56.61.Dial1.Denver1.Level3.net
66.157.197.28       2.05D+06  adsl-157-197-28.dab.bellsouth.net
209.245.13.105      2.79D+05  dialup-209.245.13.105.Dial1.Denver1.Level3.net
64.156.33.130       1.31D+06  dialup-64.156.33.130.Dial1.Denver1.Level3.net
128.117.140.86      4.68D+05  charlie.unidata.ucar.edu
128.117.140.56      1.17D+05  zero.unidata.ucar.edu
128.233.29.61       8.11D+07  tornado.usask.ca
128.117.140.107     1.15D+07  speedy.unidata.ucar.edu
128.104.110.87      5.58D+05  volante.ssec.wisc.edu
152.18.35.200       2.10D+07  mac2.atms.unca.edu
155.42.26.191       8.00D+05
128.117.140.30      4.40D+03  gilda.unidata.ucar.edu
64.230.100.25       1.84D+03  Ottawa-HSE-ppp243306.sympatico.ca
198.119.145.156     1.84D+03  buddy.larc.nasa.gov
-----------------+-----------+--------------------------------
All                 2.72D+09   33723
ADDEINFO: Done

Please let me know what you would like to do.

Tom