[RegCNET] terrrain.f
IMRAN NADEEM
qphoton at gmail.com
Sun Feb 25 23:18:47 CET 2007
Hi Jonathan,
I am sorry I mixed up ibyte and endian issue. They are totally
different issues. Actually some compilers specify record length for
unformated direct-access files in *4-byte units *and others in 1-byte
units.Thats
why we need to set ibyte=1 or 4 in domain.param. Also note that regcm always
uses big_endian (ibigend=1 in domain.param). The options -convert big_endian
or -byteswapio in Makefiles convert little endian to big_endian on machines
where internal system is little_endian.
Thank you Peter for correcting me.
Regards
Imran
On 2/23/07, Jonathan Winter <jwinter at mit.edu> wrote:
>
> Yes, I've seen ibyte in the terrain.f code and now I remember its usage.
> Thanks for the answer.
>
> jonathan
>
> On Fri, 2007-02-23 at 09:20 +0100, Peter Huszar wrote:
> > On 23/02/07, IMRAN NADEEM <qphoton at gmail.com> wrote:
> > > Hi Jonathan,
> > >
> > > You are right, this is endian issue.
> >
> > Hi Jonathan and Imram
> >
> > actually not, this is nothing to do with the big/little endian byte
> > order, but this issue is concerning the way a record is determined in
> > the direct OPEN statement. In the case of INtel compiler, the record
> > size is the number of floats represented in it, in case of PGF, it is
> > the number of bytes, which are 4 for one float number.
> >
> > Best regards
> >
> > Peter
> >
> > p.s.: What I mean in code:
> > open(unit=100,file="output.dat",access="direct",recl=(nx*ny*ibyte))
> > IFC...ibyte=1
> > PGF...ibyte=4
> >
> >
> >
> > There is a compiler dependent parameter
> > > in domain.param, ibyte. You should change ibyte according to the
> compiler
> > > you are using. (ibyte=1 for IFC8 or IFC9 and ibyte=4 for pgi compiler
> or
> > > IFC7)
> > >
> > > Regards
> > > Imran
> > >
> > >
> > > On 2/23/07, Jonathan Winter <jwinter at mit.edu> wrote:
> > > > If I compile terrain.f with IFC, then open DOMAIN.INFO with GRADS,
> the
> > > > information is incorrect (eg, all zeros for landuse, etc.). If I
> > > > compile the same code with PGI it seems to be fine. Does anyone
> know
> > > > why this is, maybe a endian issue? Just wanted to make sure other
> users
> > > > experience this and it's not specific to me. Thanks.
> > > >
> > > > jonathan
> > > >
> > > > _______________________________________________
> > > > RegCNET mailing list
> > > > RegCNET at lists.ictp.it
> > > > https://lists.ictp.it/mailman/listinfo/regcnet
> > > >
> > >
> > >
> > >
> > > --
> > > Imran Nadeem
> > > PhD Student
> > > Institute of Meteorology
> > > Department of Water, Atmosphere and Environment
> > > Uni. of Natural Resources and Applied Life Sciences (BOKU)
> > >
> > > Peter-Jordan Strasse 82
> > > 1190 Vienna, Austria
> > >
> > > Mobile: +43 699 1194 3044
> > > Tel.: +43 1 47654 5614
> > > Fax: +43 1 47654 5610
> > >
> > > _______________________________________________
> > > RegCNET mailing list
> > > RegCNET at lists.ictp.it
> > > https://lists.ictp.it/mailman/listinfo/regcnet
> > >
> > >
>
>
--
Imran Nadeem
PhD Student
Institute of Meteorology
Department of Water, Atmosphere and Environment
Uni. of Natural Resources and Applied Life Sciences (BOKU)
Peter-Jordan Strasse 82
1190 Vienna, Austria
Mobile: +43 699 1194 3044
Tel.: +43 1 47654 5614
Fax: +43 1 47654 5610
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ictp.it/pipermail/regcnet/attachments/20070225/14eec13a/attachment-0002.html>
More information about the RegCNET
mailing list