Configuration optionsΒΆ

A CATMAID instance an be configured mainly through the file, which is located in the django/projects/mysite directory. Along with (which is not supposed to be edited) the instance configuration is defined. Settings defined in can be overridden in Below is an explanation of all available settings.

Controls how many asyncronous Celery workers are allowed to run. This controls how many asyncronous tasks can be processed in parallel.
The maximum number of nodes that should be retrieved for a bounding box query as it is used to render tracing data. If set to None, no limit will be applied which can be slighly faster if node limiting isn’t necessary in most cases.
This variable takes a list of node provider names, which are iterated during a node query as long as no result data is found. The next provider, if any, is only used if the current node provider either doesn’t match the request or decides it can’t provide a useful answer. An entry can either by a single node provider name (e.g. “postgis2d”) or a tuple (name, options) to pass in additional options for a node provider. Possible node provider names are: postgis2d, postgis2dblurry, postgis3d ans postgis3dblurry. In addition to these, cache table can be configured, which allows the use of the following node proviers: cached_json, cached_json_text, cached_msgpack.
This setting specifies whether or not two default data views will be created during the initial migration of the database and is True by default. It is typically only useful if the DVID or JaneliaRender middleware are in use and doesn’t have any effect after the initial migration.
Control how many co-processes can be spawned from an async (Celery) worker. This means if MAX_PARALLEL_ASYNC_WORKERS is set to 3 and assuming CELERY_WORKER_CONCURRENCY is set to 2, asyncronous procerssing in CATMAID can be expected to use a maximum f 6 processes.