Changeset 1115 for trunk/libIGCM/libIGCM_config/libIGCM_config.ksh

Timestamp:

10/23/14 19:19:12 (10 years ago)

Author:

sdipsl

Message:

• stack files will go in /Out. see #230 Examples:
  • create_ts.19301231.2D.out
  • create_ts.19301231.2D.stack.$$
• instrumentation information will only be within stack file see #231
• plateform users should not worry about those stack files ...

File:

• trunk/libIGCM/libIGCM_config/libIGCM_config.ksh (modified) (1 diff)

trunk/libIGCM/libIGCM_config/libIGCM_config.ksh

@@ -153 +153 @@
   if ( [ X${config_Post_DodsCopy} = X${NULL_STR} ] || [ X${config_Post_DodsCopy} = X ] ) ; then
     config_Post_DodsCopy=TRUE
+  fi
+
+  #====================================================
+  # Define StackFileLocation : directory where we store stack files
+  # Define StackFileName : stack file containing call tree and instrumentation
+  # Stack file containing call tree will be stored there.
+  if ( $DEBUG_debug ) ; then
+    StackFileLocation=${StackFileLocation:=${R_BUF_KSH}}
+    [ ! -d ${StackFileLocation} ] && mkdir -p ${StackFileLocation}
+    if [ X${TaskType} = Xcomputing ]; then
+      StackFileName=computing.stack.$$
+    elif [ X${TaskType} = Xpost-processing ]; then
+      StackFileName=${Script_Post_Output}.stack.$$
+    elif [ X${TaskType} = Xchecking ]; then
+      StackFileName=checking.stack.$$
+    else
+      IGCM_debug_Exit "IGCM_config_CommonConfiguration unknown TaskType : ${TaskType}"
+      IGCM_debug_Verif_Exit
+    fi
+
+    # This boolean will trigger the filling of the stack
+    # Only now we know where things should be ...
+    ActivateStackFilling=true
   fi