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

20010209: ADDE server questions and McIDAS minor "bug" (cont.)



>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200101101820.f0AIK8o23587 McIDAS ADD web

Gilbert,

>Been real busy here, so I haven't gotten back to you on this.

No problem.

re: What I suggest is a structure that looks like:

                        /N0R/*.bref1
                        /N1R/*.bref2
   /home/data/wsr88d/FTG/N2R/*.bref3
                        /N3R/*.bref4
                        /NCR/*.cref
                        /NVL/*.vil
                        etc.
  
   The idea is for the directory structure to look like:
  
   /home/data/wsr88d/\ID/\TYPE/
  
   where \ID represents NEXRAD station IDs and \TYPE represents NEXRAD product
   types.
  
>Can you show me what the pqact.conf entry would look like? This one I am
>confused about.

Here is what we use on motherlode:

# NEXRAD feedtype,
NEXRAD  ^SDUS5. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        
data/pub/raw/nexrad/nids_(\1:yyyy)(\1:mm)\1/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

In keeping with the structure you currently have, you would probably want
to use something like:

# NEXRAD feedtype,
NEXRAD  ^SDUS5. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        /data/wsr88d/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

or

# NEXRAD feedtype,
NEXRAD  ^SDUS5. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        /data/nexrad/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

As always for pqact.conf entries, mind the tabs!

The resultant structure will end up looking like:

/data/nexrad/\ID/\TYPE/TYPE_yyyymmdd_hhmm

Or, more explicitly:

ls /data/nexrad
ABC  AMX  BMX  CLX  DOX  EVX  FWS  GYX  ICT  JGX  LTX  MOB  NQA  RAX  SRX  VBX
ABR  APD  BOX  CRP  DTX  EWX  GGW  HDX  ICX  JKL  LVX  MPX  OAX  RGX  TBW  VNX
ABX  APX  BRO  CXX  DVN  EYX  GJX  HGX  ILN  JUA  LWX  MQT  OHX  RIW  TFX  VTX
ACG  ARX  BUF  CYS  DYX  FCX  GLD  HKI  ILX  LBB  LZK  MRX  OKX  RLX  TLH  YUX
AEC  ATX  BYX  DAX  EAX  FDR  GRB  HKM  IND  LCH  MAF  MSX  OTX  RTX  TLX
AHG  BBX  CAE  DDC  EMX  FDX  GRK  HMO  INX  LIX  MAX  MTX  PAH  SFX  TWX
AIH  BGM  CBW  DFX  ENX  FFC  GRR  HNX  IWA  LNX  MBX  MUX  PBZ  SGF  TYX
AKC  BHX  CBX  DIX  EOX  FSD  GSP  HPX  IWX  LOT  MHX  MVX  PDT  SHV  UDX
AKQ  BIS  CCX  DLH  EPZ  FSX  GUA  HTX  JAN  LRX  MKX  MXX  POE  SJT  UEX
AMA  BLX  CLE  DMX  ESX  FTG  GWX  HWA  JAX  LSX  MLB  NKX  PUX  SOX  VAX

ls /data/nexrad/ABC
N0R  N0S  N0V  NCR  NTP  NVL

IF you were getting all of the NEXRAD products for station ABC.

The next thing that you have to worry about is scouring these data files.

I suggest downloading the script 'prune_nexrad.csh' from the pub/ldm5
directory of anonymous FTP on our FTP server, ftp.unidata.ucar.edu.
Read the header portion of this script to see how to configure it
and then kick off the script using cron:

#
# prune nexrad tree
#
15 * * * * util/prune_nexrad.csh >/dev/null 2>&1

Let me know if you have additional questions.

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.