[MITgcm-support] OPTFILE for IBM iDataPlex; MITgcm-support Digest, Vol 118, Issue 16
Maarten Buijsman - NOAA Affiliate
maarten.buijsman at noaa.gov
Tue Apr 30 11:27:00 EDT 2013
Hi
Thanks for yr suggestions on the optfile. My colleague Alan Wallcraft at
NRL, who is running on KILRAIN, helped me making an optfile that works!
I pasted it below. Thanks.
Maarten
====linux_amd64_ifort+mpi_idp_kilrain=================================
#!/bin/bash
#
# $Header:
/u/gcmpack/MITgcm/tools/build_options/linux_amd64_ifort+mpi_ice_nas,v 1.6
2010/10/26 19:32:04 heimbach Exp $
# $Name: checkpoint62o $
# tested on kilrain using:
# module load compiler/intel/13.0 mpi/intel/impi/4.1.0
#
#mpiifort loads MPI libraries automatically
FC=mpiifort
DEFINES='-DALLOW_USE_MPI -DALWAYS_USE_MPI -DWORDLENGTH=4'
CPP='/lib/cpp -traditional -P'
EXTENDED_SRC_FLAG='-132'
OMPFLAG='-openmp'
CFLAGS='-fPIC'
LDADD='-shared-intel'
LIBS=
INCLUDES="-I$MPI_HOME/include64"
INCLUDEDIRS=$MPI_HOME/include64
MPIINCLUDEDIR=$MPI_HOME/include64
MPI_HEADER_FILES='mpif.h mpiof.h'
MPI_HEADER_FILES_INC='./mpi_headers/mpif.h ./mpi_headers/mpiof.h'
NOOPTFLAGS='-O0 -fPIC'
if test "x$IEEE" = x ; then
# No need for IEEE-754
FFLAGS="$FFLAGS -traceback -fPIC -W0 -WB -convert big_endian -assume
byterecl -align"
FOPTIM='-O2 -ip -xSSE4.2 -fp-model source -ftz'
NOOPTFILES='seaice_growth.F calc_oce_mxlayer.F fizhi_lsm.F
fizhi_clockstuff.F'
else
# Try to follow IEEE-754
FFLAGS="$FFLAGS -traceback -fPIC -W0 -WB -convert big_endian -assume
byterecl -noalign"
FOPTIM='-O0'
fi
#- might want to use '-r8' for fizhi pkg:
#FFLAGS="$FFLAGS -r8"
#- For really big executable (> 2 GB), uncomment following 2 lines
#FFLAGS="$FFLAGS -mcmodel medium -shared-intel"
#CFLAGS='-mcmodel=medium'
====linux_amd64_ifort+mpi_idp_kilrain==================================
On Fri, Apr 26, 2013 at 12:00 PM, <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. Re: MITgcm-support Digest, 3. OPTFILE for IBM iDataPlex
> (Maarten Buijsman - NOAA Affiliate) (EAPS)
> 2. coupler and different atm/ocean grids (Maura Brunetti)
>
>
> ---------- Forwarded message ----------
> From: EAPS <ce107 at ocean.mit.edu>
> To: "mitgcm-support at mitgcm.org" <mitgcm-support at mitgcm.org>
> Cc:
> Date: Thu, 25 Apr 2013 18:28:11 -0400
> Subject: Re: [MITgcm-support] MITgcm-support Digest, 3. OPTFILE for IBM
> iDataPlex (Maarten Buijsman - NOAA Affiliate)
> 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
>
>
>
>
> ---------- Forwarded message ----------
> From: Maura Brunetti <Maura.Brunetti at unige.ch>
> To: "mitgcm-support at mitgcm.org" <mitgcm-support at mitgcm.org>
> Cc:
> Date: Fri, 26 Apr 2013 14:20:55 +0000
> Subject: [MITgcm-support] coupler and different atm/ocean grids
> Hello,
>
> I am wondering if it is possible to run the coupler with different
> cubedSphere grids for the ocean and the atmosphere, say cs64x28 for the
> ocean and cs32x15 for the atmosphere. I have tried but I get the following
> error:
>
> STOP couprecv_r8tiles: Incompatible header/target array
>
> but I'm not sure it is related to the different grids... In case it is
> possible to do this, in which subroutines the interpolation between the two
> grids are performed?
>
> Cheers,
>
> Maura
>
>
> --
> Dr. Maura Brunetti
> Institute for Environmental Sciences (ISE)
> University of Geneva
> Site de Battelle / D, 7 route de Drize
> CH-1227 Carouge / GE -- Switzerland
> Phone: +41 22 379 06 25
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20130430/51c61ceb/attachment-0001.htm>
More information about the MITgcm-support
mailing list