On Sat, Jul 28, 2012 at 6:47 PM, Nit Nit <nit...@gmail.com> wrote: >> I cannot reproduce this problem on my Linux machine. I use netcdf >> 4.1.1. It might be specific to mingw or the netcdf library. >> (there is a small typo in example_opendap: iamgesc should be imagesc, >> but this is unrelated to your problem). >> >> It is strange to have this problem when the file is closed. Are the >> variable loaded ok? Here are some elements of the variable ssh on my >> computer: >> >> >> ssh(1:5,1:5) >> ans = >> >> 0.055798 0.057120 0.058907 0.060376 0.061917 >> 0.077451 0.079210 0.081142 0.082846 0.085073 >> 0.101778 0.105107 0.108024 0.109497 0.111790 >> 0.129896 0.134813 0.137158 0.137242 0.136442 >> 0.159633 0.162679 0.163127 0.162095 0.158800 >> >> >> Also you might want to check your netcdf library using an example from >> here: >> >> http://www.unidata.ucar.edu/software/netcdf/examples/programs/simple_xy_rd.c >> >> (changing FILE_NAME to the opendap URL, size and variable name). >> >> I hope this helps, >> Cheers, >> Alex > > > Thanks Alex, > > Yes, I have noticed the image display call tipo. > > As far as I can check, the data from the url in example_opendap.m is seemed > to be read and displayed OK, and also the 5 by 5 first elements are matching > your print above. > > The only error I am getting is the ncclose error. > > It is probably a netcdf library or a dll dependency error (on my system) > because I can reproduce this error when I using pre-compiled ncdump.exe > binary supplied as part of nc4_dap_32_dll.zip together with other mingw dlls > from my system (see the printout following this message). > > I am using "ncdump,exe -h <example URL>" for just getting the header > information, and getting the same error message after the header information > is printed. I just wonder wonder why it is printed only when the file is > closed. > > BTW, I am not getting this close error with other opendap example > servers/files I have tried ! > > Nitzan > > > ******************************************************************************** > printout of ncdump.exe with the example URL > ******************************************************************************** > D:\Users\nit\My > Documents\Archives\Octave\netcdf\nc4_dap_32_dll\netcdf-windows\nc4_dap_32_dll\bin>ncdump > -h http://hycom > .coaps.fsu.edu/thredds/dodsC/atl_ops > netcdf atl_ops { > dimensions: > Depth = 33 ; > Latitude = 1609 ; > Longitude = 1678 ; > MT = 730 ; > variables: [...] > } > NetCDF: One or more variable sizes violate format constraints > Location: file ../../ncdump/ncdump.c; line 2509 > Dear Nitzan,
According to this page: http://www.unidata.ucar.edu/software/netcdf/faq-lfs.html this error might be related to the "kind of netcdf file". What do you get on your system with "ncdump -k http://hycom.coaps.fsu.edu/thredds/dodsC/atl_ops"; ? I get "64-bit offset". So maybe your library treats opendap data set as netcdf "classic" file and limiting the maximum size the dataset to 2GB. In this case you would get this error only for very large opendap data sets. Best regards, Alex ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
