[MITgcm-support] MITgcm-support Digest, 3. OPTFILE for IBM iDataPlex (Maarten Buijsman - NOAA Affiliate)
EAPS
ce107 at ocean.mit.edu
Thu Apr 25 18:28:11 EDT 2013
ia64 just happens to work on non Itanium Intel systems because generic flags are being used. amd64 is what should be used for x86_64 systems, either AMD or Intel (EMT64).
iDataplex systems belong in this latter category.
The SP* opt files work for AIX and PPC/PPC64 chips only. For LinuxPPC they will cause trouble.
Constantinos
Sent from my iPhone
On Apr 25, 2013, at 11:46 AM, Martin Losch <Martin.Losch at awi.de> wrote:
> Maarten,
>
> from here I can only guess. The best thing is you try "uname -a" and then you decide which compiler you want to use, and then you look for the appropriate opt file in tools/build_options, (where OS, chip type, and compiler agree), e.g. linux_ia64_ifort would be good starting point on a machine with linux, x86_64 chips, and ifort. That's what I use on a machine that gives
> uname -a>
> Linux uv100 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
>
> Martin
>
>
> On Apr 25, 2013, at 4:49 PM, Maarten Buijsman - NOAA Affiliate <maarten.buijsman at noaa.gov> wrote:
>
>> Hi Martin
>>
>> I am not sure if the sp[1-6] files are going to work, because it is an
>> intel chip: Intel Xeon Sandy Bridge E5-2670
>>
>> best
>> Maarten
>>
>>
>> On Wed, Apr 24, 2013 at 11:00 AM, <mitgcm-support-request at mitgcm.org> wrote:
>> Send MITgcm-support mailing list submissions to
>> mitgcm-support at mitgcm.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>> or, via email, send a message with subject or body 'help' to
>> mitgcm-support-request at mitgcm.org
>>
>> You can reach the person managing the list at
>> mitgcm-support-owner at mitgcm.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of MITgcm-support digest..."
>>
>> Today's Topics:
>>
>> 1. oneRL explicit type (Chris Horvat)
>> 2. Re: oneRL explicit type (Chris Horvat)
>> 3. OPTFILE for IBM iDataPlex (Maarten Buijsman - NOAA Affiliate)
>> 4. Re: OPTFILE for IBM iDataPlex (Martin Losch)
>>
>>
>> ---------- Forwarded message ----------
>> From: Chris Horvat <horvat at fas.harvard.edu>
>> To: MITgcm Support <mitgcm-support at mitgcm.org>
>> Cc:
>> Date: Tue, 23 Apr 2013 14:09:51 -0400
>> Subject: [MITgcm-support] oneRL explicit type
>> Hi,
>>
>> Repeatedly at compile-time, when I am trying to make my build I am running into this error
>>
>> cheapaml_coare3_flux.f(2771): error #6362: The data types of the argument(s) are invalid. [ATAN]
>> & + 4.*ATAN(oneRL)/SQRT(3.d0)
>>
>> cheapaml_coare3_flux.f(2771): error #6404: This name does not have a type, and must have an explicit type. [ONERL]
>> & + 4.*ATAN(oneRL)/SQRT(3.d0)
>>
>> is an example. All of them relate to this data ONERL
>>
>> Any help?
>>
>> Chris
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Chris Horvat <horvat at fas.harvard.edu>
>> To: MITgcm Support <mitgcm-support at mitgcm.org>
>> Cc:
>> Date: Tue, 23 Apr 2013 14:32:43 -0400
>> Subject: Re: [MITgcm-support] oneRL explicit type
>> resolved: I had an old version of eesupp/inc/EEPARAMS.h
>>
>>
>>
>>
>> On Tue, Apr 23, 2013 at 2:09 PM, Chris Horvat <horvat at fas.harvard.edu> wrote:
>> Hi,
>>
>> Repeatedly at compile-time, when I am trying to make my build I am running into this error
>>
>> cheapaml_coare3_flux.f(2771): error #6362: The data types of the argument(s) are invalid. [ATAN]
>> & + 4.*ATAN(oneRL)/SQRT(3.d0)
>>
>> cheapaml_coare3_flux.f(2771): error #6404: This name does not have a type, and must have an explicit type. [ONERL]
>> & + 4.*ATAN(oneRL)/SQRT(3.d0)
>>
>> is an example. All of them relate to this data ONERL
>>
>> Any help?
>>
>> Chris
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Maarten Buijsman - NOAA Affiliate <maarten.buijsman at noaa.gov>
>> To: mitgcm-support at mitgcm.org
>> Cc:
>> Date: Tue, 23 Apr 2013 16:49:07 -0400
>> Subject: [MITgcm-support] OPTFILE for IBM iDataPlex
>> Hi
>>
>> I wanted to do some new runs with an older MITgcm_c62o version on the NAVY DSRC computer KILRAIN which is an IBM iDataPlex. I looked for an optfile in my old MITgcm_c62o and the latest MITgcm_c64f/tools/build_options/, but could not find one.
>>
>> When I compile I do:
>> "setenv FILENM batan3D_23a ; /u/home/mbui/MITgcm_c62o/tools/genmake2 -rootdir=/u/home/mbui/MITgcm_c62o -mods=/scr/mbui/$FILENM/code -of=/u/home/mbui/MITgcm_c62o/tools/build_options/OPTFILE -disable=mnc"
>>
>> I believe NCAR also has IBM iDataPlexes.
>>
>> Does anybody has an optfile that may work with MITgcm_c62o on an IBM iDataPlex or any suggestions to modify an existing one.
>>
>> thanks a bunch
>>
>> Maarten
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Martin Losch <Martin.Losch at awi.de>
>> To: <mitgcm-support at mitgcm.org>
>> Cc:
>> Date: Wed, 24 Apr 2013 11:11:51 +0200
>> Subject: Re: [MITgcm-support] OPTFILE for IBM iDataPlex
>> Hi Maarten,
>>
>> in case of a new type of machine (I never heard of an IBM iDataPlex, but that does not mean anything) I would look for an opt file that is close to what you need (ibm compiler and libraries) and adjust paths and options according to system. The "sp[1-6]_*" files may be a good starting point.
>>
>> Martin
>>
>> On Apr 23, 2013, at 10:49 PM, Maarten Buijsman - NOAA Affiliate <maarten.buijsman at noaa.gov> wrote:
>>
>>> Hi
>>>
>>> I wanted to do some new runs with an older MITgcm_c62o version on the NAVY DSRC computer KILRAIN which is an IBM iDataPlex. I looked for an optfile in my old MITgcm_c62o and the latest MITgcm_c64f/tools/build_options/, but could not find one.
>>>
>>> When I compile I do:
>>> "setenv FILENM batan3D_23a ; /u/home/mbui/MITgcm_c62o/tools/genmake2 -rootdir=/u/home/mbui/MITgcm_c62o -mods=/scr/mbui/$FILENM/code -of=/u/home/mbui/MITgcm_c62o/tools/build_options/OPTFILE -disable=mnc"
>>>
>>> I believe NCAR also has IBM iDataPlexes.
>>>
>>> Does anybody has an optfile that may work with MITgcm_c62o on an IBM iDataPlex or any suggestions to modify an existing one.
>>>
>>> thanks a bunch
>>>
>>> Maarten
>>>
>>>
>>> _______________________________________________
>>> MITgcm-support mailing list
>>> MITgcm-support at mitgcm.org
>>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>>
>>
>>
>>
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>>
>>
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
More information about the MITgcm-support
mailing list