metgrid and FNL data

Having problems running the WRF Preprocessing Sysmte (WPS)?

metgrid and FNL data

Postby bob.bobb » Thu Mar 14, 2013 7:59 am

Hello,

I am totally new to WRF and have problems getting the version WRF 3.4.1 to run.

I have successfully (presumably) compiled WRF and WPS on my node of the cluster PC I am running WRF on. The geogrid-step works nicely, but when I try to execute the metgrid.exe, I get:

Code: Select all
Processing 2010-01-01_00
    FILE
ERROR: Didn't recognize format version of data in FILE:2010-01-01_00.\nFound version 83886080 but expected either 3, 4, or 5. This could be an endian problem.

I am using FNL- and SST-Files I received from my supervisor.

My questions:
Does anybody know this error? What can I do? Do I need a newer version of the FNL-Data?

I have not explicitly installed or configured (or executed) the ungrib-process, because according to my understanding, the FNL-data I have are already post-ungrib, so I don't have to do that step. Is that correct?

Last one: The maximum quota I have on the cluster PC I am using is exactly 83886080 blocks. Compared to the error message above, is that a coincidence?

Thank you for your help, please bear in mind that I am a total newbie,

Bob
bob.bobb
 
Posts: 11
Joined: Thu Mar 14, 2013 7:47 am

Re: metgrid and FNL data

Postby sdegan » Thu Mar 14, 2013 2:18 pm

Hi Bob,

Did you run Ungrib.exe before you ran metgrid.exe? You mentioned geogrid.exe running OK but not ungrib. If you did, did you use the correct variable table? For example, did vtables point to the fnl table and not something else like NARR?
sdegan
 
Posts: 10
Joined: Wed Jan 09, 2013 8:17 pm

Re: metgrid and FNL data

Postby bob.bobb » Wed Apr 24, 2013 8:49 am

I still have problems with WRF 3.4.

I re-downloaded FNL and SST data and ungrib-ed them, using Vtable.GFS for the FNL-data (because Vtable.NCEP wouldnt work)... did I do a mistake there?

After successful runs of geogrid.exe and metgrid.exe, the real.exe keeps crashing without any useful messages. All I get ist "Exited with exit code 127."

Does anybody know this error? It seems like this error has something to do with a faulty namelist.input file... can somebody confirm this?

Any kind of help would be appreciated!

Thanks,

Bob
bob.bobb
 
Posts: 11
Joined: Thu Mar 14, 2013 7:47 am

Re: metgrid and FNL data

Postby AchternDiek » Thu Apr 25, 2013 3:08 am

Hi Bob,

Do you get a useful message if you increase the debug level in your namelist.input?
(e.g debug level of 1000)

--AchternDiek
AchternDiek
 
Posts: 147
Joined: Wed Jun 06, 2012 6:10 am
Location: Norway

Re: metgrid and FNL data

Postby bob.bobb » Mon Apr 29, 2013 5:32 am

Hello everyone,

I still have problems with WRF 3.4. I fixed the issue above (was just a stupid broken link...), but now I have the next problem... here we go:

When I run real.exe, it runs nicely for the first of my two domains (creating wrfbdy_01, wrfinput_01 and wrfflowinp_01), but when it comes to the second domain, it fails with an "code 137" error. I think it is not an CFL-problem or anything with the domain definition in the namelist.input, because with the exact same input files, real.exe from WRF 3.2 runs without problems.

I created a small tryout case (running from 01. Jan to 04. Jan) to be able to post results here.

The rsl.error (resp. the last part of it) looks like this:

Code: Select all
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_006:000:000]
  DEBUG assemble_output:  clock after 3rd current_date set,  clock start time = 2010-01-01_00:00:00
  DEBUG assemble_output:  clock after 3rd current_date set,  clock current time = 2010-01-04_00:00:00
  DEBUG assemble_output:  clock after 3rd current_date set,  clock stop time = 2010-01-04_00:00:00
  DEBUG assemble_output:  clock after 3rd current_date set,  clock time step = 0000000000_006:000:000
 d01 2010-01-04_00:00:00 module_io.F: in wrf_ioclose
 d01 2010-01-04_00:00:00 module_io.F: in wrf_ioclose
 d01 2010-01-04_00:00:00 Timing for output          0 s.
 d01 2010-01-04_00:00:00 Timing for loop #   13 =          2 s.
 d01 2010-01-04_00:00:00 backfrom med_sidata_input
 d01 2010-01-04_00:00:00 new allocated  domain: id, par id, dims i/j, start i/j =  2  1  82 103 34 26
 d01 2010-01-04_00:00:00 parent domain: id, par id, dims i/j, start i/j =  1  0  94  94  1  1
  *************************************
  Nesting domain
  ids,ide,jds,jde             1           82            1          103
  ims,ime,jms,jme            -4           87           -4          108
  ips,ipe,jps,jpe             1           82            1          103
  INTERMEDIATE domain
  ids,ide,jds,jde            32           64           24           63
  ims,ime,jms,jme            27           69           19           68
  ips,ipe,jps,jpe            30           66           22           65
  *************************************
 d01 2010-01-04_00:00:00  alloc_space_field: domain             2 ,                 321018968  bytes allocated
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d01 2010-01-04_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_002:000:000]
  DEBUG setup_timekeeping():  clock after creation,  clock start time = 2010-01-01_00:00:00
  DEBUG setup_timekeeping():  clock after creation,  clock current time = 2010-01-01_00:00:00
  DEBUG setup_timekeeping():  clock after creation,  clock stop time = 2010-01-04_00:00:00
  DEBUG setup_timekeeping():  clock after creation,  clock time step = 0000000000_002:000:000
 d01 2010-01-04_00:00:00  setup_timekeeping:  set xtime to     0.000000
 d01 2010-01-04_00:00:00  setup_timekeeping:  set julian to     0.000000
 d01 2010-01-04_00:00:00 setup_timekeeping:  returning...
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_002:000:000]
  DEBUG real:  clock after Setup_Timekeeping,  clock start time = 2010-01-01_00:00:00
  DEBUG real:  clock after Setup_Timekeeping,  clock current time = 2010-01-01_00:00:00
  DEBUG real:  clock after Setup_Timekeeping,  clock stop time = 2010-01-04_00:00:00
  DEBUG real:  clock after Setup_Timekeeping,  clock time step = 0000000000_002:000:000
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_006:000:000]
  DEBUG real:  clock after timeStep set,  clock start time = 2010-01-01_00:00:00
  DEBUG real:  clock after timeStep set,  clock current time = 2010-01-01_00:00:00
  DEBUG real:  clock after timeStep set,  clock stop time = 2010-01-04_00:00:00
  DEBUG real:  clock after timeStep set,  clock time step = 0000000000_006:000:000
 d02 2010-01-01_00:00:00 real_em: calling set_scalar_indices_from_config
 d02 2010-01-01_00:00:00 real_em: calling model_to_grid_config_rec
 d02 2010-01-01_00:00:00 real_em: calling init_wrfio
 d02 2010-01-01_00:00:00 module_io.F: in wrf_ioinit
 d02 2010-01-01_00:00:00 Entering ext_gr1_ioinit
 d02 2010-01-01_00:00:00 real_em: re-broadcast the configuration records
 d02 2010-01-01_00:00:00 calling med_sidata_input
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_006:000:000]
  DEBUG med_sidata_input:  clock after stopTime set,  clock start time = 2010-01-01_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock current time = 2010-01-01_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock stop time = 2010-01-04_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock time step = 0000000000_006:000:000
 d02 2010-01-01_00:00:00 med_sidata_input: calling open_r_dataset for met_em.d<domain>.<date>
 d02 2010-01-01_00:00:00 module_io.F: in wrf_open_for_read
 d02 2010-01-01_00:00:00 med_sidata_input: calling input_auxinput1
 d02 2010-01-01_00:00:00  input_wrf: begin, fid =             1
  W A R N I N G : Problem opening myoutfields.txt


And the rsl.out (resp. the last part of it) looks like:

Code: Select all
Time period #   1 to process = 2010-01-01_00:00:00.
Time period #   2 to process = 2010-01-01_06:00:00.
Time period #   3 to process = 2010-01-01_12:00:00.
Time period #   4 to process = 2010-01-01_18:00:00.
Time period #   5 to process = 2010-01-02_00:00:00.
Time period #   6 to process = 2010-01-02_06:00:00.
Time period #   7 to process = 2010-01-02_12:00:00.
Time period #   8 to process = 2010-01-02_18:00:00.
Time period #   9 to process = 2010-01-03_00:00:00.
Time period #  10 to process = 2010-01-03_06:00:00.
Time period #  11 to process = 2010-01-03_12:00:00.
Time period #  12 to process = 2010-01-03_18:00:00.
Time period #  13 to process = 2010-01-04_00:00:00.
Total analysis times to input =   13.
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-01_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timetoa():  returning with str = [2010-01-04_00:00:00]
 d02 2010-01-01_00:00:00  DEBUG wrf_timeinttoa():  returning with str = [0000000000_006:000:000]
  DEBUG med_sidata_input:  clock after stopTime set,  clock start time = 2010-01-01_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock current time = 2010-01-01_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock stop time = 2010-01-04_00:00:00
  DEBUG med_sidata_input:  clock after stopTime set,  clock time step = 0000000000_006:000:000
 
 -----------------------------------------------------------------------------
 
 Domain  2: Current date being processed: 2010-01-01_00:00:00.0000, which is loop #   1 out of   13
 configflags%julyr, %julday, %gmt:         2010            1    0.000000   
 d02 2010-01-01_00:00:00 med_sidata_input: calling open_r_dataset for met_em.d<domain>.<date>
 d02 2010-01-01_00:00:00 module_io.F: in wrf_open_for_read
 d02 2010-01-01_00:00:00 med_sidata_input: calling input_auxinput1
 d02 2010-01-01_00:00:00  input_wrf: begin, fid =             1
  W A R N I N G : Problem opening myoutfields.txt


And that's where it stops. Can anybody make any sense of this infos? I can't see a clear error message anywhere, it just stops right in the middle of the run.

Like mentioned above, WRF 3.2 runs without problems on this exact case. I am very confused about this, any help would be greatly appreciated!

Bob
bob.bobb
 
Posts: 11
Joined: Thu Mar 14, 2013 7:47 am

Re: metgrid and FNL data

Postby bob.bobb » Mon Apr 29, 2013 5:54 am

For sake of completeness: I tried adding

Code: Select all
ignore_iofields_warning = .true.,


to my namelist.input to make sure the "myoutfields-warning" is not the cause of the crash, but no success there. Still real.exe crashes after having completed the first domain, as seen in my post above.
bob.bobb
 
Posts: 11
Joined: Thu Mar 14, 2013 7:47 am

Re: metgrid and FNL data

Postby bob.bobb » Tue Apr 30, 2013 4:11 am

Ok I think I solved it. I just created an empty file "myoutfields.txt" in the folder I am running WRF in, and it went through. So I think that at least in my version of WRF 3.4, there seems to be a bug with this, as the code totally ignored my

Code: Select all
ignore_iofields_warning = .true.,


line in the namelist.input and caused a fatal error anyway. Issue is closed for me then.
bob.bobb
 
Posts: 11
Joined: Thu Mar 14, 2013 7:47 am

Re: metgrid and FNL data

Postby elena.conigliaro » Mon Feb 19, 2018 7:33 am

Hi Bob,

When I try to run metgrid.exe I riceve the same error:

Processing domain 1 of 5
Processing 2018-02-10_00
GFS
ERROR: Didn't recognize format version of data in GFS:2018-02-10_00.\nFound version 83886080 but expected either 3, 4, or 5. This could be an endian problem.

How did you solve this error??

thanks for help!

Elena
elena.conigliaro
 
Posts: 2
Joined: Mon Feb 19, 2018 6:02 am


Return to Runtime Problems

Who is online

Users browsing this forum: No registered users and 2 guests