Changeset 1369


Ignore:
Timestamp:
Apr 24, 2014 5:57:38 AM (7 years ago)
Author:
raasch
Message:

routine description added, usage of module interfaces removed

Location:
palm/trunk/SOURCE
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • palm/trunk/SOURCE/cpulog.f90

    r1354 r1369  
    2020! Current revisions:
    2121! -----------------
    22 !
     22! routine description added
    2323!
    2424! Former revisions:
     
    5353! Description:
    5454! ------------
    55 ! Cpu-time measurements for any program part whatever.
     55! CPU-time measurements for any program part whatever. Results of the
     56! measurements are output at the end of the run in local file CPU_MEASURES.
     57!
     58! To measure the CPU-time (better to say the wallclock time) of a specific code
     59! segment, two calls of cpu_log have to be used as brackets in front and at the
     60! end of the segment:
     61!
     62!     CALL cpu_log( log_point(n), 'any identifier', 'start' )
     63!       ... code segment ...
     64!     CALL cpu_log( log_point(n), 'any identifier', 'stop' )
     65!
     66! Parts of the code segment can be excluded from the measurement by additional
     67! call of cpu_log:
     68!
     69!       ... first segment to be measured
     70!     CALL cpu_log( log_point(n), 'any identifier', 'pause' )
     71!       ... oart of segment to be excluded from measurement
     72!     CALL cpu_log( log_point(n), 'any identifier', 'continue' )
     73!       ... second segment to be mesasured
     74!
     75! n is an INTEGER within the interval [1,100] defining the id of the specific
     76! code segment, 'any identifier' is a string describing the code segment to be
     77! measured. It can be freely chosen and results will appear under this name in
     78! file CPU_MEASURES. ids can only be used once. If you like to do a
     79! measurement of a new part of the code, please look for an id which is unused
     80! ao far.
     81!
     82! d3par-parameter cpu_log_barrierwait can be used to set an MPI barrier at the
     83! beginning of the measurement (modus 'start' or 'continue'), to avoid that
     84! idle times (due to MPI calls in the code segment, which are
     85! waiting for other processes to be finished) affect the measurements.
     86! If barriers shall not be used at all, a fourth, optional parameter has to be
     87! given:
     88!
     89!     CALL cpu_log( ..., ..., 'start', cpu_log_nowait )
     90!
     91! Variable log_point should be used for non-overlapping code segments, and they
     92! should sum up to the total cpu-time required by the complete run.
     93! Variable log_point_s can be used for any other special (s) measurements.
    5694!------------------------------------------------------------------------------!
    5795
  • palm/trunk/SOURCE/lpm_advec.f90

    r1360 r1369  
    2020! Current revisions:
    2121! ------------------
    22 !
     22! usage of module interfaces removed
    2323!
    2424! Former revisions:
     
    6464
    6565    USE cpulog
    66 
    67     USE interfaces
    6866
    6967    USE pegrid
Note: See TracChangeset for help on using the changeset viewer.