Re: [ldm-users] ldmadmin watch output question

• To: evan@xxxxxxxxxxxx, ldm-users@xxxxxxxxxxxxxxxx
• Subject: Re: [ldm-users] ldmadmin watch output question
• From: "Kevin W. Thomas" <kwthomas@xxxxxxxxxxxxxxxxxx>
• Date: Wed, 14 Aug 2019 19:08:03 -0500 (CDT)

Evan...

NEXRAD2 data arrives in a modified BZIP2 format.  If I recall correctly,
it is in groups of 100 radials that are compressed though the number may 
have changed over the years.

There is just too much data to send not compressed, and this was well
before dual pol.

I did some benchmark tests *many* years ago.  Back then, space saving was on
the order of 85%, though this was probably without much precip.

Sites may or may not decompress the data before writing.  CAPS writes it
compressed, as our ARPS software decompresses it on the fly.

To answer your question, one number is probably the compressed size and
the other thd decompressed size.

        Kevin W. Thomas
        Center for Analysis and Prediction of Storms
        University of Oklahoma
        Norman, Oklahoma
        Email:  kwthomas@xxxxxx

>ldm@dallas-tx-1:~$ ldmadmin watch 2>&1 | grep NEXRAD2
>20190814T194054.858618Z               pqutil[30750]
>pqutil.c:display_watch() INFO       79987 20190814184136.177460 NEXRAD2
>591026  L2-BZIP2/KCXX/20190814183810/591/26/I/V06/0
>
>In the above output, what is the significance of 79987 and 591026.  Is one
>the file size, or both together comprise the filesize?  Offset?  I would
>appreciate any insight here.

• Follow-Ups:
  • Re: [ldm-users] ldmadmin watch output question
    • From: Karen Cooper - NOAA Affiliate