/[MITgcm]/MITgcm/model/src/write_state.F

Diff of /MITgcm/model/src/write_state.F

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

-revision 1.14 by heimbach,
Tue Aug 14 00:20:49 2001 UTC
+revision 1.15 by cnh,
Wed Sep 26 18:09:16 2001 UTC
 Line 2 
 C $Header$
  C $Name$
  #include "CPP_OPTIONS.h"
- C--  File read_write.F: Routines to handle mid-level I/O interface.
- C--   o WRITE_STATE - Write out model state.
- C The following CPP flag (MULTIPLE_RECORD_STATE_FILES) is
- C #define/#undefed here since it is specific to this routine and
- C very user-preference specific.
- C
- C If #undefed (default) the state files are written as in all versions
- C prior to checkpoint32, where a file is created per variable, per time
- C and per tile. This *has* to be the default because most users use this
- C mode and all utilities and scripts (diagnostic) assume this form.
- C It is also robust, as explained below.
- C
- C If #defined, subsequent snap-shots are written as records in the
- C same file (no iteration number in filenames).
- C Advantages: - fewer files
- C             - for small problems, is easy to copy the output around
- C Disadvantages:
- C             - breaks a lot of diagnostic scripts
- C             - for large or long problems this creates huge files
- C             - is an unexpected, unsolicited change in behaviour which came
- C               as a surprise (in c32) and inconvenience to several users
- C             - can not accomodate changing the frequency of output
- C               after a pickup (this is trivial in previous method
- C               but needs new code and parameters in this new method)
- C Known Bugs:
- C             - if the length of integration is not exactly an integer
- C               times the output frequency then the last record written
- C               (at end of integration) overwrites a previously written
- C               record corresponding to an earier time. *BE WARNED*
  #undef  MULTIPLE_RECORD_STATE_FILES
- CStartofinterface
+ CBOP
+ C     !ROUTINE: WRITE_STATE
+ C     !INTERFACE:
        SUBROUTINE WRITE_STATE ( myCurrentTime, myIter, myThid )
- C     /==========================================================\
+ C     !DESCRIPTION: \bv
- C     | SUBROUTINE WRITE_STATE                                   |
+ C     *==========================================================*
- C     | o Controlling routine for IO to dump model state.        |
+ C     | SUBROUTINE WRITE_STATE
- C     |==========================================================|
+ C     | o Controlling routine for IO to dump model state.
- C     | Write model state files for post-processing. This file   |
+ C     *==========================================================*
- C     | includes code for diagnosing W and RHO for output.       |
+ C     | Write model state files for post-processing. This file
- C     \==========================================================/
+ C     | includes code for diagnosing W and RHO for output.
-       IMPLICIT NONE
+ C     | File write_state.F: Routines to handle mid-level I/O
+ C     | interface.
+ C     | o WRITE_STATE - Write out model state.
+ C     | The following CPP flag (MULTIPLE_RECORD_STATE_FILES) is
+ C     | #define/#undefed here since it is specific to this routine
+ C     | and very user-preference specific.
+ C     |
+ C     | If #undefed (default) the state files are written as in all versions
+ C     | prior to checkpoint32, where a file is created per variable, per time
+ C     | and per tile. This *has* to be the default because most users use this
+ C     | mode and all utilities and scripts (diagnostic) assume this form.
+ C     | It is also robust, as explained below.
+ C     |
+ C     | If #defined, subsequent snap-shots are written as records in the
+ C     | same file (no iteration number in filenames).
+ C     | Advantages: - fewer files
+ C     |       - for small problems, is easy to copy the output around
+ C     | Disadvantages:
+ C     |       - breaks a lot of diagnostic scripts
+ C     |       - for large or long problems this creates huge files
+ C     |       - is an unexpected, unsolicited change in behaviour which came
+ C     |         as a surprise (in c32) and inconvenience to several users
+ C     |       - can not accomodate changing the frequency of output
+ C     |         after a pickup (this is trivial in previous method
+ C     |         but needs new code and parameters in this new method)
+ C     | Known Bugs:
+ C     |       - if the length of integration is not exactly an integer
+ C     |         times the output frequency then the last record written
+ C     |         (at end of integration) overwrites a previously written
+ C     |         record corresponding to an earier time. *BE WARNED*
+ C     *==========================================================*
+ C     \ev
+ C     !USES:
+       IMPLICIT NONE
  C     == Global variables ===
  #include "SIZE.h"
  #include "EEPARAMS.h"
-Line 56 
 C     == Global variables ===
+Line 58 
 C     == Global variables ===
  #ifdef ALLOW_PASSIVE_TRACER
  #include "TR1.h"
  #endif
        LOGICAL  DIFFERENT_MULTIPLE
        EXTERNAL DIFFERENT_MULTIPLE
        INTEGER  IO_ERRCOUNT
        EXTERNAL IO_ERRCOUNT
+ C     !INPUT/OUTPUT PARAMETERS:
  C     == Routine arguments ==
  C     myThid - Thread number for this instance of the routine.
  C     myIter - Iteration number
-Line 69 
 C     myCurrentTime - Current time of si
+Line 71 
 C     myCurrentTime - Current time of si
        _RL     myCurrentTime
        INTEGER myThid
        INTEGER myIter
- CEndofinterface
+ C     !LOCAL VARIABLES:
  C     == Local variables ==
        CHARACTER*(MAX_LEN_MBUF) suff
        INTEGER iRec
+ CEOP
        IF (
       &     DIFFERENT_MULTIPLE(dumpFreq,myCurrentTime,

 Legend:



Removed from v.1.14
 


changed lines


 
Added in v.1.15
 Legend:



Removed from v.1.14
 


changed lines


 
Added in v.1.15
-Removed from v.1.14
+Added in v.1.15

	ViewVC Help
Powered by ViewVC 1.1.22