How many seconds to wait for network requests between CryoSPARC master/master processes before timing out with an error
The amount of time to wait (in seconds) in between status updates for cluster jobs.
The maximum amount of retries for cluster job status updates.
The amount of time to wait (in milliseconds) for the database to respond when starting it.
In master/worker or cluster modes, Import Jobs always run on the default master node. Set this to
true to allow running them on any node
In master/worker or cluster modes,
cryosparcm commands always run on the machine where
cryosparc_master was initially installed. Set this to
true to allow running on any machine
cryosparcm commands must be run by the same UNIX user account that owns the
cryosparc_master installation. Set this to
true to allow running
cryosparcm from any user account
Override the installed master hostname when checking that
cryosparcm is running on the correct host. See also
When checking that job directory is empty before running a job, set to
true to ignore any filenames that being with
.. Use this if your file system or OS automatically creates hidden files
true to run the script specified in
CRYOSPARC_LIVE_DATA_MANAGEMENT_SCRIPT_PATH every time a CryoSPARC Live session's data management status changes. See Live Session Data Management Tutorial
The path to a bash script that runs every time a session's data management status changes: See Live Session Data Management Tutorial. Use this to perform archive or deletion processes specific to your system (e.g., move archive data to an S3 bucket). The script is given arguments for the project UID, session UID, the datatype that changed (
thumbnails), and the status of that datatype (
How much RAM to allocate for MongoDB database query cache, in GB
How many CPU cores to allocate for each GPU used in Patch, Full-frame and Local Motion Correction jobs
How much RAM (in MB) to allocate for each GPU used in Patch, Full-frame and Local Motion Correction jobs
The prefix to add to a project directory name on the filesystem when it is created.
If set, CryoSPARC makes an HTTP request to this URL each time a job's status changes with some job metadata encoded in JSON
Whenever a job requires SSD cache, it automatically checks for and removes files that haven't been accessed in more than the number of days specified by this variable. Note: Files may remain on the SSD for longer than this amount since they only get cleaned up when a job runs
true to prevent the application from requesting external HTTPS resources used to display information modules on the homepage.
May be required for connection to the CryoSPARC license verification server on systems with outdated Certificate-Authority files or that filter HTTPS requests through a proxy. Specify a path to a file or folder that contains the certificates