Difference between revisions of "TIEGCM"

From Tau Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 31: Line 31:
 
After TAU is built setup your environment for TAU by doing:
 
After TAU is built setup your environment for TAU by doing:
  
  export TAU_MAKEFILE=/glade/home/sbiersdo/tau-2.21.1/ibm64/lib/Makefile.tau-mpi-pdt
+
  export TAU_MAKEFILE=<path to TAU>/ibm64/lib/Makefile.tau-mpi-pdt
 
  export TAU_OPTIONS='-optKeepFiles -optVerbose -optCPPReset="-WF,-DAIX,-DMPI"'
 
  export TAU_OPTIONS='-optKeepFiles -optVerbose -optCPPReset="-WF,-DAIX,-DMPI"'
  
Line 57: Line 57:
 
COUPLING  := NO
 
COUPLING  := NO
 
EXECNAME  := tiegcm.x
 
EXECNAME  := tiegcm.x
 +
TAU_MAKEFILE := <path to TAU>/ibm64/lib/Makefile.tau-mpi-pdt
 +
TAU_OPTIONS  := '-optKeepFiles -optVerbose -optCPPReset="-WF,-DAIX,-DMPI"  -optTauSelectFile="select.tau"'
 +
MPIF90    := tau_f90.sh -tau_makefile=$(TAU_MAKEFILE) -tau_options=$(TAU_OPTIONS)
 
MPI      := TRUE
 
MPI      := TRUE
 
</pre>
 
</pre>
 +
 +
With this selective instrumentation file:
 +
 +
<pre>
 +
BEGIN_FILE_EXCLUDE_LIST
 +
 +
wei01gcm.F
 +
wei05sc.F
 +
 +
END_FILE_EXCLUDE_LIST
 +
</pre>
 +
 +
saved as '''select.tau''' in the src directory
 +
 +
%> MAKE_MACHINE=Make.bluefire make
  
 
== Running TIEGCM ==
 
== Running TIEGCM ==
 +
 +
For example simulation the 5-day control run started from steady-state histories at the December solstice (solar maximum). In your run script you will want the set:
 +
 +
setenv TAU_TRACK_SIGNALS 1
 +
mpirun.lsf /usr/local/bin/launch ./tiegcm.x < tiegcm_decsol_smax.inp >& tiegcm_decsol_smax.out
 +
 +
== Performance Data ==
 +
 +
Coming soon.

Latest revision as of 00:33, 29 February 2012


Background

Link Code Version Machine Date
HAO website 1.94 Bluefire February 2012

Building PDT

./configure --xlC -arch=ibm64
make 
make install

Building TAU

./configure -arch=ibm64 -cc=xlc_r -c++=xlC_r -fortran=ibm64 -pdt=<path to pdtoolkit-3.17> -mpi
make install 

After TAU is built setup your environment for TAU by doing:

export TAU_MAKEFILE=<path to TAU>/ibm64/lib/Makefile.tau-mpi-pdt
export TAU_OPTIONS='-optKeepFiles -optVerbose -optCPPReset="-WF,-DAIX,-DMPI"'

Building TIEGCM

You will need a version of gmake to compile TIEGCM, so make sure the 'make' command will use gmake:

make -v
GNU Make ...

copy over the scripts you will need:

cd src ; cp ../scripts/Make.bluefire .

modify the Makefile to include these variables:

OS        := $(shell uname -s)
VPATH     := $(subst $(space),:,$(DIRS))
INC_DIRS  := $(foreach dir,$(DIRS),-I$(dir)) -I. -I$(INC_NETCDF)
SOURCES   := $(shell cat Srcfiles)
SOURCES   := $(addsuffix .f, $(basename $(SOURCES)))
OBJS      := $(addsuffix .o, $(basename $(SOURCES)))
DIRS      := `pwd`
LIBS      += -L$(LIB_NETCDF) -lnetcdf
COUPLING  := NO
EXECNAME  := tiegcm.x
TAU_MAKEFILE := <path to TAU>/ibm64/lib/Makefile.tau-mpi-pdt
TAU_OPTIONS  := '-optKeepFiles -optVerbose -optCPPReset="-WF,-DAIX,-DMPI"  -optTauSelectFile="select.tau"'
MPIF90    := tau_f90.sh -tau_makefile=$(TAU_MAKEFILE) -tau_options=$(TAU_OPTIONS)
MPI       := TRUE

With this selective instrumentation file:

BEGIN_FILE_EXCLUDE_LIST

wei01gcm.F
wei05sc.F

END_FILE_EXCLUDE_LIST

saved as select.tau in the src directory

%> MAKE_MACHINE=Make.bluefire make

Running TIEGCM

For example simulation the 5-day control run started from steady-state histories at the December solstice (solar maximum). In your run script you will want the set:

setenv TAU_TRACK_SIGNALS 1
mpirun.lsf /usr/local/bin/launch ./tiegcm.x < tiegcm_decsol_smax.inp >& tiegcm_decsol_smax.out

Performance Data

Coming soon.