/[MITgcm]/MITgcm/eesupp/src/eeboot.F

Diff of /MITgcm/eesupp/src/eeboot.F

Parent Directory | Revision Log | View Revision Graph Revision Graph | View Patch Patch

-revision 1.2 by cnh,
Thu Apr 23 20:37:29 1998 UTC
+revision 1.26 by jmc,
Thu Sep 14 19:47:35 2017 UTC
 Line 1
  C $Header$
+ C $Name$
  #include "CPP_EEOPTIONS.h"
+ #include "PACKAGES_CONFIG.h"
- CStartOfInterface
+ CBOP
-       SUBROUTINE EEBOOT
+ C     !ROUTINE: EEBOOT
- C     /==========================================================\
- C     | SUBROUTINE EEBOOT                                        |
- C     | o Set up execution "environment", particularly perform   |
- C     |   steps to initialise parallel processing.               |
- C     |==========================================================|
- C     | Note: This routine can also be compiled with CPP         |
- C     | directives set so that no multi-processing is initialised|
- C     | This is OK and should work fine.                         |
- C     \==========================================================/
+ C     !INTERFACE:
+       SUBROUTINE EEBOOT( myComm )
+ C     !DESCRIPTION:
+ C     *==========================================================*
+ C     | SUBROUTINE EEBOOT
+ C     | o Set up execution "environment", particularly perform
+ C     |   steps to initialise parallel processing.
+ C     *==========================================================*
+ C     | Note: This routine can also be compiled with CPP
+ C     | directives set so that no multi-processing is initialised
+ C     | This is OK and works fine.
+ C     *==========================================================*
+ C     !CALLING SEQUENCE:
+ C     eeboot()
+ C       |
+ C       |-- eeboot_minimal() :: Minimal startup. Just enough to
+ C       |                       allow basic I/O.
+ C       |
+ C       |-- eeintro_msg()    :: Write startup greeting.
+ C       |
+ C       |-- eeset_parms()    :: Set WRAPPER parameters
+ C       |
+ C       |-- eewrite_eeenv()  :: Print WRAPPER parameter settings
+ C       |
+ C       |-- ini_procs()      :: Associate processes with grid regions.
+ C       |
+ C       |-- ini_threading_environment() :: Associate threads with grid regions.
+ C       |
+ C       |-- cpl_register()   :: Pass attributes to the coupler
+ C       |
+ C       |-- w2_eeboot()      :: Initialise WRAPPER2 execution environment
+ C     !USES:
+       IMPLICIT NONE
  C     == Global variables ==
  #include "SIZE.h"
  #include "EEPARAMS.h"
  #include "EESUPPORT.h"
- CEndOfInterface
+ C     !ROUTINE ARGUMENTS
+ C     == Routine arguments ==
+ C     myComm     :: Communicator that is passed down from
+ C                   upper level driver (if there is one).
+       INTEGER myComm
+ C     !LOCAL VARIABLES:
  C     == Local variables ==
- C     msgBuf - Variable for building informational messages
+ C     I :: Loop counter
- C     I - Loop counter
        INTEGER I
-       CHARACTER*(MAX_LEN_MBUF) msgBuf
+       LOGICAL doReport
+ CEOP
  C--   Set error reporting flags and I/O streams
  C     fatalError is a flag used to indicate that the program
-Line 36 
 C                          writing textu
+Line 71 
 C                          writing textu
  C     eeBootError is a flag used to indicate an error in the
  C                "execution environment" startup pahse as opposed
  C                to the simulation pahse of the execution.
  C     eeEndError is used to indicate an "execution environment" shutdown
  C                error.
  C     thError flag used to allow a thread to report an error.
  C             This is only really used during the startup process,
  C             although it could be used elsewhere.
  C     allMyEdgesAreSharedMemory flag which says for a particular
  C                               set of blocks the only form of communication
  C                               it does is using shared memory.
  C     threadIsRunning used during startup to enable check that all
  C                     the threads are running.
        fatalError          = .FALSE.
-       errorMessageUnit    = 0
-       standardMessageUnit = 6
        eeBootError         = .FALSE.
        eeEndError          = .FALSE.
        DO I=1, MAX_NO_THREADS
-Line 56 
 C                     the threads are ru
+Line 89 
 C                     the threads are ru
         allMyEdgesAreSharedMemory(I) = .TRUE.
         threadIsRunning(I)           = .FALSE.
         threadIsComplete(I)          = .FALSE.
+        ioErrorCount(I)              = 0
        ENDDO
-       scrUnit1      = 11
+       standardMessageUnit = 6
-       scrUnit2      = 12
+ #ifdef HACK_FOR_GMAO_CPL
-       eeDataUnit    = 13
+       scrUnit1            = 31
-       modelDataUnit = 14
+       scrUnit2            = 32
- C     Annoyingly there is no universal way to have the usingMPI
+       eeDataUnit          = 33
- C     parameter work as one might expect. This is because, on some
+       modelDataUnit       = 34
- C     systems I/O does not work until MPI_Init has been called. The
+       errorMessageUnit    = 35
- C     solution for now is that the parameter below may need to be changed
+ #else
- C     manually!
+       scrUnit1            = 11
- #ifdef ALLOW_USE_MPI
+       scrUnit2            = 12
-       usingMPI = .TRUE.
+       eeDataUnit          = 13
+       modelDataUnit       = 14
+       errorMessageUnit    = 15
+ cph   errorMessageUnit = 0 is not allowed on some platforms, e.g. SP3
  #endif
- C--   Start minimal environment so that we can do I/O
+ C--   Start minimal environment so that we can do I/O to report errors.
- C--   to report errors.
  C     Notes
  C     =====
  C     o Here we start MPI and setup the I/O environment
- C       thatis needed for error reporting.
+ C       that is needed for error reporting.
  C     o Under MPI I/O support is very variable until
  C       MPI is started. This makes is hard to trap the case
  C       where mpirun is used to start a non-MPI run or
  C       we try to start MPI when mpirun was not used.
  C       after it is started.
-       CALL EEBOOT_MINIMAL
+ C jmc: test:
+ C     If necessary ( COMPONENT_MODULE defined ) add a 1rst preliminary
+ C     call to eeset_params (in EEBOOT_MINIMAL) to set useCoupler (needed
+ C     very early, and the stardard call eeset_params below comes too late)
+ C jmc: This needs to be sorted-out in a cleaner way.
+       CALL EEBOOT_MINIMAL( myComm )
        IF ( eeBootError ) GOTO 999
  C--   Now we can write a startup message
        CALL EEINTRO_MSG
  C--   Initialise parameters associated with execution environment.
-       CALL EESET_PARMS
+       doReport = .TRUE.
+       CALL EESET_PARMS ( myProcId, doReport )
        IF ( eeBootError ) GOTO 999
  C--   Write summary of execution environment configuration for this run
-Line 97 
 C--   Write summary of execution environ
+Line 139 
 C--   Write summary of execution environ
  C--   Now do the rest of the multi-process startup.
  C     o Here we map processes to the model grid.
  C     o Print tables of process-grid mappings.
  C     o Do other miscellaneous multi-processing set up steps. For
  C       example under MPI we create datatypes for communication
  C       of array edges.
        CALL INI_PROCS
-Line 108 
 C     o Note the program is still runnin
+Line 150 
 C     o Note the program is still runnin
  C       execution at this stage.
        CALL INI_THREADING_ENVIRONMENT
        IF ( eeBootError ) GOTO 999
+ #ifdef ALLOW_EXCH2
+ C--   Initialise WRAPPER2 execution environment
+       CALL W2_EEBOOT
+ #endif /* ALLOW_EXCH2 */
+ C--   Pass attributes to the coupler
+ #ifdef COMPONENT_MODULE
+       IF ( useCoupler ) CALL CPL_REGISTER
+ #endif
 CONTINUE
        RETURN
        END
- C $Id$

 Legend:



Removed from v.1.2
 


changed lines


 
Added in v.1.26
 Legend:



Removed from v.1.2
 


changed lines


 
Added in v.1.26
-Removed from v.1.2
+Added in v.1.26

	ViewVC Help
Powered by ViewVC 1.1.22