read new monitoring.summary_file option

Author: oesteban

doc/users/config_file.rst

@@ -166,9 +166,10 @@ Resource Monitor
     Sampling period (in seconds) between measurements of resources (memory, cpus)
     being used by an interface (default value: ``1``)
 
-*summary_path*
-    Path where the summary ``resource_monitor.json`` should be stored, when running
-    a workflow (``summary_path`` does not apply to interfaces run independently).
+*summary_file*
+    Indicates where the summary file collecting all profiling information from the
+    resource monitor should be stored after execution of a workflow.
+    The ``summary_file`` does not apply to interfaces run independently.
     (unset by default, in which case the summary file will be written out to 
     ``<base_dir>/resource_monitor.json`` of the top-level workflow).
 

nipype/pipeline/engine/utils.py

@@ -1304,12 +1304,17 @@ def write_workflow_resources(graph, filename=None, append=None):
     in a pandas DataFrame or processed with JavaScript like D3.js
     """
     import simplejson as json
+
+    # Overwrite filename if nipype config is set
+    filename = config.get('monitoring', 'summary_file', filename)
+
+    # If filename still does not make sense, store in $PWD
     if not filename:
         filename = os.path.join(os.getcwd(), 'resource_monitor.json')
 
     if append is None:
         append = str2bool(config.get(
-            'execution', 'resource_monitor_append', 'true'))
+            'monitoring', 'summary_append', 'true'))
 
     big_dict = {
         'time': [],