[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #ZRX-231843]: [netcdfgroup] Segmentation fault using Compound-type in NetCDF4 files


> Recently I created a program to read .csv files into NetCDF4 files. The code 
> did not show any error-messages while compiling and the NetCDF4 files have 
> always been created. However, if I try to retrieve the data, I get a 
> "segmentation fault" due to the built-in compound dimension/variable "time". 
> Does anybody know how I can fix this? Thx!

Could you make available a copy of the netCDF-4 file that has this problem?
That way we could see if we can duplicate the problem with the current version 
ncdump, diagnose it, and fix it.

> Further information:
> Â         The program was written on Python 3.2 using Python interface to 
> netCDF version 4 library 
> (http://netcdf4-python.googlecode.com/svn/trunk/docs/netCDF4-module.html )
> Â         To retrieve the data I used:
> o   Command "ncdump" from the NetCdf4 library on Linux ,written in C 
> (http://linux.die.net/man/1/ncdump)

What version of ncdump?  To find out, look at the last line of output from
ncdump -version.

> o   Command "ncdump -x" from the NetCdf4 library on Linux ,written in C

The documentation for the -x option says it only works for netCDF classic files.
It hasn't yet been upgraded to handle the netCDF-4 data model, including any
user-defined types.

> o   Command "ncks" from the NCO (NetCDF Operator)  library using Cygwin on 
> Windows (http://nco.sourceforge.net/ )

The documantation for nco says it hasn't been fully upgraded to handle the 
data model yet, including user-defined types.


Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: ZRX-231843
Department: Support netCDF
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.