[gradsusr] GRADS1.9 OS X compiling problem --- big endian vs. small endian

[Jennifer Adams]

On Feb 11, 2011, at 6:16 PM, Malte Stuecker wrote:

> Dear Arlindo,
>
> Thank you very much for the information, I wasn't aware of the  
> opengrads project. This helps a lot!
> I briefly had a look at grads v2, however wasn't convinced.
You should look through the list of new features and bug fixes in the  
changelog and see if any of those affect the work you do with GrADS.
http://iges.org/grads/changelog-2.0.txt

> I use mainly netcdf files with a no leap calender and the new  
> version doesn't automatically recognize the 365 day calender in  
> contrast to grads 1.9.
Not recognizing 365-day-calendars with sdfopen is a bug fix! The way  
that the sdfopen code figures out the initial time and time increment  
in a netcdf file is by using the udunits library, which does not  
recognize 365-day calendars. Initial time values determined by sdfopen  
may often be severely wrong! There were also well-documented memory  
leaks in the sdfopen code in v1.9. Please see http://gradsusr.org/pipermail/gradsusr/2009-December/010064.html

Version 1.9 is no longer being actively supported at COLA.

Jennifer



>
> Kind regards,
> Malte
>
> 2011/2/11 Arlindo da Silva <dasilva at alum.mit.edu>
> On Thu, Feb 10, 2011 at 3:15 PM, Malte Stuecker <malte.stuecker at gmail.com 
> > wrote:
> Hi,
>
> I have a problem getting GRADS 1.9 running on my OS X 10.5 machine.
> I first downloaded the pre-compiled darwin version from the website  
> and everything is running (incl. netcdf),
> however, on the starting screen GRADS states "big endian". The OSX  
> 10.5 is small endian to my knowledge. I used the big endian grads  
> version
> on some data files and everything seems working. Should I be   
> concerned that some data might be wrong because I am using a big  
> endian software on a small endian machine?
>
> This is probably a powerpc binary. I would not worry about it  
> (much). Just make sure that binary files have .ctl that explicitly  
> states the endianess of the file through the OPTIONS keywork.
>
> I also tried compiling the source files, however I can only get  
> gradsc compiled and not netcdf, opendap etc, even though the  
> libraries are in the standard directories.
>
> Have you tried the opengrads binaries? There you will find an Intel  
> Mac build:
>
>     http://sourceforge.net/projects/opengrads/files/grads1/1.10.r2/
>
> The is version 1.10.r2.oga, which should have the same features of  
> GrADS v1.9 with the addition of the opengrads extensions.  More  
> information here:
>
>      http://opengrads.org/wiki/index.php?title=Installing_the_OpenGrADS_Bundle
>
> Unless you have a good reason for using grADS v1.x, I strong  
> recommend you upgrade to GrADS v2.
>
>    Arlindo
>
>
>
> -- 
> Arlindo da Silva
> dasilva at alum.mit.edu
>
> _______________________________________________
> gradsusr mailing list
> gradsusr at gradsusr.org
> http://gradsusr.org/mailman/listinfo/gradsusr
>
>
> _______________________________________________
> gradsusr mailing list
> gradsusr at gradsusr.org
> http://gradsusr.org/mailman/listinfo/gradsusr

--
Jennifer M. Adams
IGES/COLA
4041 Powder Mill Road, Suite 302
Calverton, MD 20705
jma at cola.iges.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gradsusr.org/pipermail/gradsusr/attachments/20110211/ea9b28cc/attachment-0003.html