ext_pkg_open_for_write_begin Error

Having problems running the WRF Preprocessing Sysmte (WPS)?

ext_pkg_open_for_write_begin Error

Postby gbromley_wisc » Thu Jun 28, 2018 12:57 pm

I am getting this error using version 4.0 of WPS/WRF. It occurs in my metgrid output on the cheyenne cluster. the software I am using are the ones precompiled on cheyenne (with support for large files). The metgrid job will fail at random dates. I cannot seem to reproduce the same failures. Does anyone have any ideas? Let me know what other information would be helpful!

Thanks!

namelist.wps:

&share
wrf_core = 'ARW',
max_dom = 1,
start_date = '2015-04-01_00:00:00',
end_date = '2015-07-01_00:00:00',
interval_seconds = 21600
io_form_geogrid = 2,
opt_output_from_geogrid_path = '/glade/work/gbromley/wrf_data/geogrid_output/20km_wrf/',
/

&geogrid
parent_id = 1,
parent_grid_ratio = 1,
i_parent_start = 1,
j_parent_start = 1,
e_we = 74,
e_sn = 61,
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
! The default datasets used to produce the HGT_M, GREENFRAC,
! and LU_INDEX/LANDUSEF fields have changed in WPS v3.8. The HGT_M field
! is now interpolated from 30-arc-second USGS GMTED2010, the GREENFRAC
! field is interpolated from MODIS FPAR, and the LU_INDEX/LANDUSEF fields
! are interpolated from 21-class MODIS.
!
! To match the output given by the default namelist.wps in WPS v3.7.1,
! the following setting for geog_data_res may be used:
!
! geog_data_res = 'gtopo_10m+usgs_10m+nesdis_greenfrac+10m','gtopo_2m+usgs_2m+nesdis_greenfrac+2m',
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
geog_data_res = 'gtopo_30s+modis_15s+modis_lai'
dx = 20000,
dy = 20000,
map_proj = 'lambert',
ref_lat = 45.000,
ref_lon = -105.000,
truelat1 = 50.000,
truelat2 = 40.000,
stand_lon = -105.000,
geog_data_path = '/glade/p/work/wrfhelp/WPS_GEOG/'
/

&ungrib
out_format = 'WPS',
prefix = 'FILE',
/

&metgrid
fg_name = 'FILE' 'PRES',
io_form_metgrid = 2,
opt_output_from_metgrid_path = '/glade/scratch/gbromley/metgrid_data/',

/
gbromley_wisc
 
Posts: 4
Joined: Thu Mar 31, 2016 3:25 pm

Re: ext_pkg_open_for_write_begin Error

Postby dcvz » Thu Jun 28, 2018 4:50 pm

In fg_name, shouldn't there be a comma between 'FILE' and 'PRES'?
dcvz
 
Posts: 165
Joined: Tue Apr 15, 2008 12:02 am

Re: ext_pkg_open_for_write_begin Error

Postby gbromley_wisc » Fri Jun 29, 2018 4:09 pm

I did modify the namelist as suggested, but metgrid still fails. It got through a month of era-interim data before failing.
gbromley_wisc
 
Posts: 4
Joined: Thu Mar 31, 2016 3:25 pm

Re: ext_pkg_open_for_write_begin Error

Postby dcvz » Fri Jun 29, 2018 6:27 pm

The ext_pkg_open_for_write_begin can mean the disk is full or not writable. Maybe you hit a quota? The obvious thing to try next is to break up the time period into smaller chunks (2 weeks?). I'd also suggest emailing wrfhelp since they have experience using cheyenne.
dcvz
 
Posts: 165
Joined: Tue Apr 15, 2008 12:02 am


Return to Runtime Problems

Who is online

Users browsing this forum: No registered users and 4 guests