[Wrf-users] OBSGRID and MADIS MESONET data

[Bart Brashers]

Does anyone have a suggestion for OBSGRID's QC settings, for use the MADIS MESONET data?

I'm investigating using MADIS data, as processed through OBSGRIDv3.4.0, for OBS nudging (obs_nudge_opt = 0, 0, 1,) in WRFv3.5.1.  MADIS data contains MESONET data as one of its streams - there's lots of data there, but of unknown quality.  Fortunately, OBSGRID's namelist has in &record4 a bunch of settings for Quality Control.

One of my 5.5-day WRF runs (starting at 2011-07-05_12) crashes, and I've narrowed it down to the use of MESONET data.  There were no CFL errors, but 7 of the 64 threads crashed, e.g.

---------------------
$ tail rsl.error.0013
****** CALL IN4DOB AT KTAU = 13428 AND XTIME =    2238.00:  NSTA =    6333 ******
 ++++++CALL ERROB AT KTAU = 13428 AND INEST =  3:  NSTA =  6333 ++++++

 REPORTING OBS MASS-PT LOCS FOR NEST    3 AT XTIME=  2238.0 MINUTES
 FREQ=  30, MAX=   10 LOCS, NEWLY READ OBS ONLY, -999 => OBS OFF PROC

     OBS#     I       J       K     OBS LAT  OBS LON   XLAT(I,J)  XLONG(I,J)  TIME(hrs)  OBS STATION ID
      6312  88.754 295.035   1.000   45.350 -111.734   -999.000   -999.000    38.27       ENNM8

[compute-0-5:28270] *** Process received signal ***
[compute-0-5:28270] Signal: Segmentation fault (11)
[compute-0-5:28270] Signal code: Address not mapped (1)
[compute-0-5:28270] Failing at address: 0xfffffffe0471ead0
[compute-0-5:28270] *** End of error message ***
---------------------

>From my namelist.oa:

&record4
 qc_test_error_max           = .TRUE.
 qc_test_buddy               = .TRUE.
 qc_test_vert_consistency    = .TRUE.
 qc_test_convective_adj      = .TRUE.
 max_error_t                 = 5
 max_error_uv                = 13
 max_error_z                 = 8
 max_error_rh                = 25
 max_error_p                 = 600
 max_buddy_t                 = 8
 max_buddy_uv                = 8
 max_buddy_z                 = 8
 max_buddy_rh                = 40
 max_buddy_p                 = 800
 buddy_weight                = 1.0
 max_p_extend_t              = 1300
 max_p_extend_w              = 1300
/

Any suggestions for how to diagnose this problem?  I've looked through the OBS_DOMAIN301 file, and as far as I can see there's nothing really bad around the time of the crash (2011-07-07_01) nor with the entry for station ENNM8.

Bart Brashers
bbrashers at environcorp.com


________________________________
This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to email at environcorp.com and immediately delete all copies of the message.