BeckyThanks.Eric, Wojciech -- some of our users are noting issues with the 40km NAM files since the upgrade. Can you please take a look?Sorry -- should have read the entire thread. Mike confirmed in another email that he pulled down the awip3d 40km file and it also seemed to have the corruption.I'll pull in some other folks now.On Wed, Mar 22, 2017 at 10:01 PM, Rebecca Cosgrove - NOAA Federal <address@hidden> wrote:BeckyMore to come in the morning.Then if one of you on this thread can pull down that full file from our ftp server and see if you get the same corruption we'll know which avenue to go down in our troubleshooting. I want to make sure it's not our breaking up of the file before I bring in the model developer.Dataflow -- can you tell us the equivalent files on ftpprd to the 40km ones we send to CONDUIT?Hi Folks.Let's try something. I want to see if it's the 40km grids themselves, or something about the way we're breaking them up to insert into the LDM for CONDUIT.On Wed, Mar 22, 2017 at 9:06 PM, Tyle, Kevin R <address@hidden> wrote:Mike, I am seeing the exact same error as you with the 40 km NAM grids since the upgrade.
_____________________________________________
Kevin Tyle, Manager of Departmental Computing
Dept. of Atmospheric & Environmental Sciences
University at Albany
Earth Science 235, 1400 Washington Avenue
Albany, NY 12222
Email: address@hidden
Phone: 518-442-4578
_____________________________________________
From: address@hidden.edu <address@hidden.edu > on behalf of Mike Leuthold <address@hidden>
Sent: Wednesday, March 22, 2017 6:03:07 PM
To: address@hidden
Subject: [conduit] Unable to initialize WRF using NAM212 (awip3d) since the upgrade on 3/21I am getting an error with real.exe in seemingly random times. I don't
actually think it's a CONDUIT problem as I downloaded the awip3d
directly and get the same problem.
Domain 1: Current date being processed: 2017-03-24_06:00:00.0000, which
is loop # 13 out of 29
configflags%julyr, %julday, %gmt: 2017 83 6.000000
metgrid input_wrf.F first_date_input = 2017-03-24_06:00:00
metgrid input_wrf.F first_date_nml = 2017-03-22_18:00:00
Ignoring all time series locations beyond # 1. Increase max_ts_locs in
namelist.input
Timing for input 1 s.
flag_soil_layers read from met_em file is 1
Using sfcprs3 to compute psfc
i,j = 515 114
target pressure and value = 11.06958 -2.457370
column of pressure and value = 11.49449 0.0000000E+00
column of pressure and value = 11.47927 128.0209
column of pressure and value = 11.45342 346.5604
column of pressure and value = 11.42688 569.4280
column of pressure and value = 11.39957 796.8333
column of pressure and value = 11.37142 1029.564
column of pressure and value = 11.34235 1269.082
column of pressure and value = 11.31232 1515.348
column of pressure and value = 11.28131 1769.324
column of pressure and value = 11.24930 2031.577
column of pressure and value = 11.21623 2302.089
column of pressure and value = 11.18206 2580.684
column of pressure and value = 11.14673 2867.329
column of pressure and value = NaN -2202740.
column of pressure and value = 8.517193 20560.38
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 5108
troubles, could not find trapping x locations
I think this is a corruption of only the 40km grids as I manually
downloaded the 32km awip32 grids from the same time and it did work.
Unfortunately, the 32km is not available on CONDUIT and I'd MUCH prefer
using CONDUIT NAM grids rather than downloading from NCEP. Anyone have
any ideas?
thanks.
Mike
--
Mike Leuthold
Manager, Regional Weather Modeling Program
University of Arizona, Atmospheric Sciences
520-282-1478 (cell)
520-621-2863 (office)
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
conduit mailing list
address@hidden
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
conduit mailing list
address@hidden
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
_______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. conduit mailing list address@hidden For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/