[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #KFD-709221]: GEMPAK Help Needed!

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [GEMPAK #KFD-709221]: GEMPAK Help Needed!
  • Date: Tue, 30 Apr 2013 15:27:31 -0600
Hello all,


From Steve Chiswell, former developer here at Unidata:

"When text is backwards and flipped 4321 or 21 43 as below, the problem is the 
MCHPRM defines the wrong machine type byteorder. Eg, they have created 
something that doesn't match, 
or used a compile flag (such a gnu has) than defines byteorder which doesn't 
match the expected routine #ifdef's. 

Also, if files are being created huge, then you probably need to define 
unspecified reals and integers as 4 bytes. The compiler may be defining them as 
I*8 or I*16 by default for the system. 

Steve"

1) MTMACH is what to check in the files in $GEMPAK/include/gemprm.h against the 
compiler options used in $NAWIPS/config/Makeinc.* files

2) try forcing with flags -i4  and -r8

-Michael



> Thanks Reuben,
> 
> I don't see anything obvious in the log that tells me what is going wrong.  I 
> hesitated before to suggest you upgrade to the latest GEMPAK 6.8.0 because 
> I'm not sure how easy that is on these machines.  If you can, I would suggest 
> a clean build of 6.8.0 as there have been a lot of configuration and build 
> changes since 5.11.4, and of course there have been a LOT of code updates.
> 
> I may forward this to our previous GEMPAK developer who has more experience 
> building with the pgi compilers.  For now, my next step would be to 
> completely turn off all optimization and attempt the build again (a full 
> build with "make distclean").
> 
> Lastly, if you have any logs or text output of the endian errors, please send 
> them my way.
> 
> Michael
> 
> 
> > Attached is an output of the compilation I have.
> >
> > Thank you,
> > Reuben
> >
> > On Friday, April 26, 2013 04:29:11 pm Kevin W. Thomas wrote:
> > > >Forgot to mention, please send along any compilation logs you have,
> > > >thanks!
> > > >
> > > >-Michael
> > > >
> > > >Ticket Details
> > > >===================
> > > >Ticket ID: KFD-709221
> > > >Department: Support GEMPAK
> > > >Priority: Normal
> > > >Status: Open
> > >
> > > Reuben...
> > >
> > > Can you do this?
> > >
> > > Thanks!
> > >
> > >   == kwthomas ==
> >
> > --
> > Reuben D. Budiardja
> > Scientific Computing Group
> > National Institute for Computational Sciences (NICS)
> > The University of Tennessee
> >
> >
> 

Ticket Details
===================
Ticket ID: KFD-709221
Department: Support GEMPAK
Priority: Normal
Status: Open