Re: [Opengrads-devel] Merging and reconciling GrADS v2.0.a3

[Jennifer A. <jm...@co...>]

On Aug 15, 2008, at 9:40 AM, Arlindo da Silva wrote:

> On Fri, Aug 15, 2008 at 8:58 AM, Jennifer Adams <jm...@co...>  
> wrote:
> Arlindo --
> I am happy to hear 2.0.a3 built (almost) perfectly with your  
> supplibs and passed your tests. Was the change from Pixel to  
> gaPixel the only change needed to get the GUI to build?
>
> Yep, besides the build being able to detect libsx, etc.
Good. That's easy.
>
> Did you try out the sdfwrite command?
>
> Not yet. My plan is to write a test for it adapting what I had for  
> lats in v1.9. (Data is written out using sdfwrite, read back and  
> compared to what we started with.)
The netcdf files created by sdfwrite are type NC_DOUBLE (since that's  
how the variable is defined in memory). Next round will include  
netcdf4, so we can enable compression to make the output file smaller.

>
>
> The mods you outline below seem fine with me, but I will check with  
> Brian about the main() changes.
>
> In a way, this is mainly organizational, as I already had Win32  
> ifdef's around main in there. This way I do not have to pollute  
> grads.c with Win32 specific stuff. You do not have to do anything  
> with main_win32.c right now; I am waiting for the build to settle  
> for me to wire that in.
>
> I asked him about /pytests and he would prefer that there is no  
> dependence on python at all, even just for testing.
>
> It is not a dependence like the others: if python with the vanilla  
> standard libraries is not present then "make check" will not work.  
> Except for a very old sun, I am yet to find a platform where python  
> does not come standard. It is almost like depending on sh(1) these  
> days. But OK, it is not a big deal.
>
> Seems like an easy enough thing to package separately, if people  
> who are building from source want to use to check on their work.
>
> Consider using it yourself, you do not need to know python to read  
> the "OK's" :-).
yuk yuk yuk
I can understand "OK", but can my computer???
# OK
tcsh: OK: Command not found.


> Seriously, you can also add tests by providing a gs script with  
> your tests.
I will likely just adapt the python stuff to use GrADS scripts. I  
think a test suite is a good idea.

>
>   Have a nice vacation!
Thanks! I will be checking email sporadically.
--Jennifer