[MITgcm-support] IBM

[Martin Losch]

Hi again,
thanks, Stefano, I'll try that as well, but just "/" work well, too.

Chris,
did you have a look at the figure that I send with my last "complaint"? 
Is your suspicion about WORDLENGTH/big/little endian based on that 
figure? Can you explain why, because I see the problems only along the 
tile edges. With a big/little endian issue I would expect trouble 
everywhere.

I won't have time to work on this before Thursday, when I'll have 
someone with me who knows more about the specific configuration of our 
IBM. You'll hear from me (o:

Martin


On Monday, May 10, 2004, at 11:24 AM, quero_s at libero.it wrote:

> Hi,
> just an "aesthetic" note.
> I run MITgcm on a SP4 platform and using
>
> &END
>
> as namelist terminator there are no "warning" messages.
> However, as Patrick said, the execution is not influenced using & .
>
> Stefano
>
>> I might suspect a big-endian / little-endian thing at this point or 
>> the
>> direct access file wordlength parameter - WORDLENGTH=
>>
>> Chris
>>
>>> -----Original Message-----
>>> From: mitgcm-support-bounces at mitgcm.org
>>> [mailto:mitgcm-support-bounces at mitgcm.org] On Behalf Of Martin Losch
>>> Sent: Friday, May 07, 2004 11:14 AM
>>> To: mitgcm-support at mitgcm.org
>>> Subject: Re: [MITgcm-support] IBM
>>>
>>> Well, with xlf,  there is a runtime option:
>>> via the environment variable XLFRTEOPTS you can set the name list
>>> behavior either setenv XLFRTEOPTS namelist=old or setenv XLFRTEOPTS
>>> namelist=new (default) but in both cases the & as the namelist
>>> terminator does not seem to be allowed. But as Patrick pointed out 
>>> the
>>> program complains but the execution is not affected. The problems I 
>>> am
>>> having stem from something different, that must be related to MPI or
>>> exchanges in general, because I see ridiculous values in Eta (-536 to
>>> 8) and W after the first time step. It must be something really
>>> stupid. Patrick just pointed out to me usingMPI=.true. in eedata, but
>>> that didn't do it, what about the other settings in eedata (taken 
>>> from
>>> the verification experiments global_ocean.cs32x15)? I don't know
>>> anything about that.
>>>
>>> Martin
>>>
>>> PS. Maybe the attached figure helps (SSH after 1 timestep, plotted
>>> range is +/-1m, actual range is -580 to 8m)
>>>
>>>
>>
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
>>
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-support