File tree Expand file tree Collapse file tree 1 file changed +9
-2
lines changed Expand file tree Collapse file tree 1 file changed +9
-2
lines changed Original file line number Diff line number Diff line change @@ -60,8 +60,12 @@ It is not always easy to estimate the amount of resources a particular function
60
60
or command uses. To help with this, Nipype provides some feedback about the
61
61
system resources used by every node during workflow execution via the built-in
62
62
runtime profiler. The runtime profiler is automatically enabled if the
63
- ``psutil `` Python package is installed and found on the system. If the package
64
- is not found, the workflow will run normally without the runtime profiler.
63
+ psutil _ Python package is installed and found on the system.
64
+
65
+ .. _psutil : https://pythonhosted.org/psutil/
66
+
67
+ If the package is not found, the workflow will run normally without the runtime
68
+ profiler.
65
69
66
70
The runtime profiler records the number of threads and the amount of memory (GB)
67
71
used as ``runtime_threads `` and ``runtime_memory_gb `` in the Node's
@@ -121,6 +125,9 @@ Visualizing Pipeline Resources
121
125
Nipype provides the ability to visualize the workflow execution based on the
122
126
runtimes and system resources each node takes. It does this using the log file
123
127
generated from the callback logger after workflow execution - as shown above.
128
+ The pandas _ Python package is required to use this feature.
129
+
130
+ .. _pandas : http://pandas.pydata.org/
124
131
125
132
::
126
133
from nipype.pipeline.plugins.callback_log import log_nodes_cb
You can’t perform that action at this time.
0 commit comments