Changeset 1369 for palm/trunk

Timestamp:

Apr 24, 2014 5:57:38 AM (11 years ago)

Author:

raasch

Message:

routine description added, usage of module interfaces removed

Location:

palm/trunk/SOURCE

Files:

• cpulog.f90 (modified) (2 diffs)
• lpm_advec.f90 (modified) (2 diffs)

palm/trunk/SOURCE/cpulog.f90

@@ -20 +20 @@
 ! Current revisions:
 ! -----------------
-! 
+! routine description added
 ! 
 ! Former revisions:
@@ -53 +53 @@
 ! Description:
 ! ------------
-! Cpu-time measurements for any program part whatever.
+! CPU-time measurements for any program part whatever. Results of the
+! measurements are output at the end of the run in local file CPU_MEASURES.
+!
+! To measure the CPU-time (better to say the wallclock time) of a specific code
+! segment, two calls of cpu_log have to be used as brackets in front and at the
+! end of the segment:
+!
+!     CALL cpu_log( log_point(n), 'any identifier', 'start' )
+!       ... code segment ...
+!     CALL cpu_log( log_point(n), 'any identifier', 'stop' )
+!
+! Parts of the code segment can be excluded from the measurement by additional
+! call of cpu_log:
+!
+!       ... first segment to be measured
+!     CALL cpu_log( log_point(n), 'any identifier', 'pause' )
+!       ... oart of segment to be excluded from measurement
+!     CALL cpu_log( log_point(n), 'any identifier', 'continue' )
+!       ... second segment to be mesasured
+!
+! n is an INTEGER within the interval [1,100] defining the id of the specific
+! code segment, 'any identifier' is a string describing the code segment to be
+! measured. It can be freely chosen and results will appear under this name in
+! file CPU_MEASURES. ids can only be used once. If you like to do a
+! measurement of a new part of the code, please look for an id which is unused
+! ao far.
+!
+! d3par-parameter cpu_log_barrierwait can be used to set an MPI barrier at the
+! beginning of the measurement (modus 'start' or 'continue'), to avoid that
+! idle times (due to MPI calls in the code segment, which are
+! waiting for other processes to be finished) affect the measurements.
+! If barriers shall not be used at all, a fourth, optional parameter has to be
+! given:
+!
+!     CALL cpu_log( ..., ..., 'start', cpu_log_nowait )
+!
+! Variable log_point should be used for non-overlapping code segments, and they
+! should sum up to the total cpu-time required by the complete run.
+! Variable log_point_s can be used for any other special (s) measurements.
 !------------------------------------------------------------------------------!
 

palm/trunk/SOURCE/lpm_advec.f90

@@ -20 +20 @@
 ! Current revisions:
 ! ------------------
-! 
+! usage of module interfaces removed
 ! 
 ! Former revisions:
@@ -64 +64 @@
 
     USE cpulog
-
-    USE interfaces
 
     USE pegrid