6

我遇到了一个 python 脚本的问题,该脚本从 grib2 格式的天气模型 (GFS) 下载最近的天气数据。它以前可以工作,但现在不能了(即在 GFS 服务器上下载最近的文件)。尝试访问数据时,我遇到了分段错误,我什至不知道从哪里开始。下面是两个示例(工作和不工作)。我运行 linux mint cinnamon。我安装了 python-grib 和 python3-grib(版本:1.9.8-1build2,通过软件管理器)。

任何建议将不胜感激。

Ps:给我分段错误的文件示例在这里: http: //www.ftp.ncep.noaa.gov/data/nccf/com/gfs/prod/gfs.2015013000/ 文件名:gfs.t00z。 master.grbf003.10m.uv.grib2

我认为,较旧的文件不会保存在该服务器上。不过,可以在此处找到一个示例: http ://grib.virtual-loup-de-mer.org/archives/2014/0130/ 文件名:gfs.t00z.master.grbf03.10m.uv.grib2

Pps:抱歉拖了这么久。我已经从 1.98 安装了 pygrib 2.0 版,它现在可以工作了。Arghh,我花了很长时间才尝试这个(并实际正确安装它)。但就是这样。无论如何,对所有答案的每个人都表示“感谢”,laetitia

/usr/bin/python3.4

Python 3.4.0 (default, Apr 11 2014, 13:05:11) 
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

工作脚本:

import pygrib

grbs = pygrib.open('winddata1.grib2')

for grb in grbs:

...     grb

... 

1:10 metre U wind component:m s**-1 (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201411041200
2:10 metre V wind component:m s**-1 (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201411041200

grb = grbs.message(1)

wind = grb.data(lat1=20,lat2=70,lon1=220,lon2=320)

quit()

/usr/bin/python3.4

Python 3.4.0 (default, Apr 11 2014, 13:05:11) 
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

失败的脚本:

import pygrib

grbs = pygrib.open('winddata2.grib2')

for grb in grbs:
...     grb
... 
1:10 metre U wind component:m s**-1 (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201501220600

2:10 metre V wind component:m s**-1 (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201501220600

grb = grbs.message(1)

wind = grb.data(lat1=20,lat2=70,lon1=220,lon2=320)

错误:

Segmentation fault

编辑(希望这是有道理的)

运行(作为脚本 testing.py)给了我:

gdb -ex r --args /usr/bin/python3.4 testing.py

GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python3.4...(no debugging symbols found)...done.
Starting program: /usr/bin/python3.4 testing.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
1:10 metre U wind component:m s**-1    (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201501220600
2:10 metre V wind component:m s**-1 (instant):regular_ll:heightAboveGround:level 10 m:fcst time 0 hrs:from 201501220600

Program received signal SIGSEGV, Segmentation fault.
0x000000000053b684 in PyLong_AsVoidPtr ()
(gdb) bt
#0  0x000000000053b684 in PyLong_AsVoidPtr ()
#1  0x00007ffff5968da7 in ?? () from /usr/lib/python3/dist-packages/numpy/core/multiarray.cpython-34m-x86_64-linux-gnu.so
#2  0x0000000000533cd2 in PyObject_AsReadBuffer ()
#3  0x00007ffff21c9f00 in ?? () from /usr/lib/python3/dist-packages/g2clib.cpython-34m-x86_64-linux-gnu.so
#4  0x000000000057bf33 in PyEval_EvalFrameEx ()
#5  0x000000000057d3d3 in PyEval_EvalCodeEx ()
#6  0x000000000057df80 in ?? ()
#7  0x000000000043810a in PyObject_Call ()
#8  0x00000000004d3745 in ?? ()
#9  0x000000000043810a in PyObject_Call ()
#10 0x00007ffff677669c in ?? () from /usr/lib/python3/dist-packages/pygrib.cpython-34m-x86_64-linux-gnu.so
#11 0x000000000043810a in PyObject_Call ()
#12 0x00007ffff675788a in ?? () from /usr/lib/python3/dist-packages/pygrib.cpython-34m-x86_64-linux-gnu.so
#13 0x00007ffff6762ece in ?? () from /usr/lib/python3/dist-packages/pygrib.cpython-34m-x86_64-linux-gnu.so
#14 0x000000000057bf33 in PyEval_EvalFrameEx ()
#15 0x000000000057d3d3 in PyEval_EvalCodeEx ()
#16 0x000000000060ba83 in PyRun_FileExFlags ()
#17 0x000000000060bc85 in PyRun_SimpleFileExFlags ()
#18 0x000000000060d3ac in Py_Main ()
#19 0x000000000041ec0d in main ()
4

1 回答 1

2

您正在运行什么版本的 pygrib 库?http://pygrib.googlecode.com/svn/trunk/Changelog上的发行说明描述了几种情况,其中制作了新版本来处理导致段错误的问题。我会拉下最新的,看看这个错误是否仍然存在。

于 2015-02-04T15:42:26.760 回答