Project

General

Profile

CDO Runtime error Windows 7

Added by Zuzana Kupcihova over 7 years ago

Hi,
I am analyzing 20gb nc file which contains 6-hourly data. I want to compute the daily mean with:
cdo daymean infile ofile

But after a while it always ends with an error:

Assertion failed: pxp->bf_offset <=offset && offset < pxp/>bf_offset + (off_t) pxp/>bf_extent, file posixio.c, line 325

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.

Can somebody help me?
Thanks


Replies (17)

RE: CDO Runtime error Windows 7 - Added by Rocio Aguero over 7 years ago

Hello. Could you find out what the problem was? I get the same error while trying cdo sinfo command. I`m analyzing a 5gb nc file, with the win32 version. Could that be the problem? I`m new at CDO

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

the plain win32 binary has a 2GB limitation due to netcdf3 usage. netcdf4 cannot be cross-compiled with mingw, that's why we changed to cygwin based build: https://code.zmaw.de/attachments/download/12761/cdo-1.7.2-cygwin64.zip

I offers a lot more features than the cross-compiled version.

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

The cdo-1.7.2-cygwin64 doesn't work, because there is no .dll file in the respective .zip...

It says:
The program can't start because cyggomp-1.dll is missing from your computer. Try reinstalling the program to fix the problem.

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

I read that it is not safe to download this file from 'free .dll sites'. Could you please add this to the cdo-1.7.2-cygwin64.zip?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

cygwin is a complete unix-like environment for windows: http://www.cygwin.com/

you have to install it before you can use the CDO binary in cdo-1.7.2-cygwin64.zip

Basically it offers a command line inter face better than cmd.exe and access to prebuild packages (with or without graphical user interface)

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

So I've been reading the FAQ about the cygwin and it says that there are many different packages to install within. Which ones do I need to run the CDO?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

I listed them here: Win32 If you do not want to build any other software, that should sufficient.

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

I installed cygwin with the following packages: netcdf,udunits, libproj.
How does it work now? How do I run the CDOs?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

you unpack the zip file for cygwin and copy the cod.exe to /usr/bin

doing thin in native windows, the correct path should look like c:\cygwin64\bin

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

and after this you have to open a new cygwin terminal to check it cdo works

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

Still a problem... Something's missing?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

missing openmp: install the gcc-core and gcc-g++ packages

hth
ralf

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

It helped, thanks a lot!
Just one more question, how do I access the .nc files that I have somewhere on my computer using Cygwin terminal?
What is the path to get to C://something?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

the windows volumes (C:, D:,...) are accessable via /cygdrive/c or /cygdrive/d

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

And where do I find cygdrive?

RE: CDO Runtime error Windows 7 - Added by Ralf Mueller over 7 years ago

just type

ls /
and for your C drive
ls /cygdrive/c

RE: CDO Runtime error Windows 7 - Added by Zuzana Kupcihova over 7 years ago

Thank you, everything works fine now :)

    (1-17/17)