I've not seen that problem with either OpenDX or non-OpenDX compliant netCDFs, from a variety of different sources. I took a very quick look at your netCDFs. The array sizes are certainly not big, so it's not a memory issue (as reported with ncdump -h). I've used much bigger arrays with netCDF files. I tried reading it with OpenDX 4.2. The importer didn't crash, but complained that it couldn't find a positions variable. That means that one of your fields has a specification for positions pointing to another variable in the file, which Import can't find. I did not go through your netCDF metadata to verify that all of the references were there. But I hope this gives you a clue. [EMAIL PROTECTED]@opendx.watson.ibm.com on 08/28/2002 02:15:16 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: [opendx-users] Importing Large NetCDF files into OpenDX I've been trying to import two netCDF files that I ran the ncdx utility on in order to make them OpenDX compliant. Each time I've run into a segmentation fault (signal 11) that disconnects the ui from the executive server. I understand this is a memory problem, but I'm not sure exactly of the problem's characteristics or how to rectify it. Can anyone help? I've made these files (originally generated by HOPs, made OpenDX compliant by ncdx) available here: http://web.mit.edu/revprez/Public/netcdf I'd appreciate any insight on my problem. Peace.
