You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/users/config_file.rst
+31-22Lines changed: 31 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@
6
6
7
7
Some of the system wide options of Nipype can be configured using a
8
8
configuration file. Nipype looks for the file in the local folder under the name
9
-
``nipype.cfg`` and in ``~/.nipype.cfg`` (in this order). If an option will not
10
-
be specified a default value will be assumed. The file is divided into following
11
-
sections:
9
+
``nipype.cfg`` and in ``~/.nipype/nipype.cfg`` (in this order). If an option
10
+
will not be specified a default value will be assumed. The file is divided into
11
+
following sections:
12
12
13
13
Logging
14
14
~~~~~~~
@@ -25,7 +25,7 @@ Logging
25
25
values: ``INFO`` and ``DEBUG``; default value: ``INFO``)
26
26
*log_to_file*
27
27
Indicates whether logging should also send the output to a file (possible
28
-
values: ``true`` and ``false``; default value: ``true``)
28
+
values: ``true`` and ``false``; default value: ``false``)
29
29
*log_directory*
30
30
Where to store logs. (string, default value: home directory)
31
31
*log_size*
@@ -120,43 +120,52 @@ Example
120
120
hash_method = timestamp
121
121
display_variable = :1
122
122
123
-
Additionally you can set some config options by setting the workflow.config. This, however, currently does not work for options related to logging levels. Those will be always read from .cfg files.
124
-
125
-
Workflow.config property has a form of a nested dictionary reflecting the structure of the .cfg file.
123
+
Workflow.config property has a form of a nested dictionary reflecting the
0 commit comments