On a related note, is there any way to tell MPAS to read coarser geo data than the 30sec data? Because I'm only running at 240 km resolution, 30-arc-second geo data seems like overkill. It takes ~20 minutes to go through one set of 30-arc-second files for the entire globe, so it took almost an hour and a half to get to that error.
The last several lines of the log.0000.err file:
BEGIN INTERPOLATION OF STATISTICAL FIELDS FOR GRAVITY WAVE DRAG OVER OROGRAPHY
min MeshD = 1.0000000000000000
max MeshD = 1.0000000000000000
min dcEdge = 200090.77843043293
max dcEdge = 254288.69858080952
dir_gwdo = orogwd_2deg
/Users/tsupinie/wrf/geog/orogwd_2deg/con/00001-00180.00001-00090
--- end interpolate CON
/Users/tsupinie/wrf/geog/orogwd_2deg/oa1/00001-00180.00001-00090
--- end interpolate OA1
/Users/tsupinie/wrf/geog/orogwd_2deg/oa2/00001-00180.00001-00090
--- end interpolate OA2
/Users/tsupinie/wrf/geog/orogwd_2deg/oa3/00001-00180.00001-00090
--- end interpolate OA3
/Users/tsupinie/wrf/geog/orogwd_2deg/oa4/00001-00180.00001-00090
--- end interpolate OA4
/Users/tsupinie/wrf/geog/orogwd_2deg/ol1/00001-00180.00001-00090
--- end interpolate OL1
/Users/tsupinie/wrf/geog/orogwd_2deg/ol2/00001-00180.00001-00090
--- end interpolate OL2
/Users/tsupinie/wrf/geog/orogwd_2deg/ol3/00001-00180.00001-00090
--- end interpolate OL3
/Users/tsupinie/wrf/geog/orogwd_2deg/ol4/00001-00180.00001-00090
--- end interpolate OL4
/Users/tsupinie/wrf/geog/orogwd_2deg/var/00001-00180.00001-00090
--- end interpolate VAR2D
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x1008e4e8d
#1 0x1008e539b
#2 0x7fff888431b9
#3 0x1000dd11f
#4 0x100103e94
#5 0x1001df71d
I don't know if I'll get any particularly useful responses, since I suspect it has to do with the fact that I'm running this on OS X, and a lot of people prefer Linux. But I thought I'd ask anyway.
Thanks!
Tim Supinie
To unsubscribe from this group and stop receiving emails from it, send an email to mpas-atmosphere-help+unsub...@googlegroups.com.
Worked fine at 120km, successful runs with live FILE* from our daily GARW runs, cool graphics using NCL), but init_atmo crashed using either the 60km and 30km meshes with errors in the pnetcdf libraries, ncmpii_mgetput (nonblocking.c), called ultimately from mpas_io.F.
Based on the advice upthread, edited mpas_io.F in the region of lines 259-276 to set pio_iotype to PIO_iotype_netcdf rather than PIO_iotype_pnetcdf (and changed pio_mode appropriately). That "fixed" the problem . . . will keep poking at it, but it seems to be in the pnetcdf/pio world. Made a brief detour into PIO2 but had trouble with clean compile and was impatient so reverted to netcdf4.1.3/pio1.9.23. Note this only seems to happen in init_atmosphere_model, so far the model itself seems to work fine on the unedited code.
Thanks,
Chuck
Chuck Watson