The cryoSPARC master node hosts the web server and manages job resource allocation.
Workstations or master nodes with a
cryosparc_master installation have access to
cryosparcm, cryoSPARC's built-in command-line utility for all administrative, management and advanced usage tasks.
To use it, log into the machine onto which cryoSPARC was installed. Open a Terminal running a shell (such as
bash) and enter any of the commands described below.
See Software Updates for details.
Apply the latest patches available for your installed version of cryoSPARC without doing a full version update.
--help flag to see full usage
$ cryosparcm patch --helpusage: cryosparcm patch [-h] [-f] [-y] [--check] [--download] [--install]Download and apply cryoSPARC patches. Run cryosparcm patch to automaticallyinstall the latest patches on master and worker nodesoptional arguments:-h, --help show this help message and exit-f, --force install latest patch again even if already installed-y, --yes confirm patch installation without prompt--check check to see if a patch is available--download download master and worker patches for manual installation--install manually install a downloaded patch file
Frequently used commands:
cryosparcm patch: Automatically installs the latest patches on workstations or master node and connected workers. Not recommended for clusters: Use the
--install flags instead.
cryosparcm patch --force: Reinstalls the latest patches in case something went wrong with a previous attempt
cryosparcm patch --check: Shows information about the latest patches without installing
cryosparcm patch --download: Downloads the latest patches without installing them. Follow the resulting instructions to install the master and worker patches
cryosparcm patch --install: Run this command immediately after a
--download to install the patch on the master node.
Configures cluster installation. See the Download and Installation page for details.
Use with one of the following sub-commands.
Writes config and script template files to current working directory,
Examples are available for Portable Batch System (
cryosparcm cluster example pbs) and SLURM (
cryosparcm cluster example slurm) schedulers. Other systems are similar; run one of the two
cluster example commands and modify the output files accordingly.
Outputs the existing config and script to current working directory for the cluster with the given name.
cluster_script.sh from the current directory. Connects a new or updates an existing cluster configuration using the name from
Removes a cluster configuration from the scheduler.
The following commands are only allowed to be executed by
<cryosparcuser> (the user that installed cryoSPARC), and can only be executed on the master node. If these conditions are not met, you may see the following error:
You can mitigate errors temporarily by specifying the
CRYOSPARC_FORCE_HOSTNAME variable just before calling the command:
email@example.com:~$ CRYOSPARC_FORCE_HOSTNAME="true"firstname.lastname@example.org:~$ cryosparcm status----------------------------------------------------------------------------CryoSPARC System master node installed at/home/cryosparcuser/cryosparc/cryosparc_master----------------------------------------------------------------------------cryosparcm process status:...
If this error message is incorrect (the hostname specified in the error message is actually the same host, just a different identifier), you can set the hostname that the management script will use to compare by adding the variable
cryosparc_master/config.sh. You can also set
CRYOSPARC_FORCE_HOSTNAME in this file to permanently suppress this error.
File: /home/cryosparcuser/cryosparc/cryosparc_master/config.shexport CRYOSPARC_LICENSE_ID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"export CRYOSPARC_MASTER_HOSTNAME="uoft"export CRYOSPARC_DB_PATH="/home/cryosparcuser/cryosparc/cryosparc_master"export CRYOSPARC_BASE_PORT=61000export CRYOSPARC_HOSTNAME_CHECK="uoft"
Prints out current status of the cryoSPARC master system, including the status of all individual processes (
command_core, etc). Also prints out configuration environment variables.
Starts the cryoSPARC instance if stopped, including the database, the command server, the web interface, etc.
All processes start in the background, including all jobs and the web interface; the command line may be closed after running
Stops the cryoSPARC instance if running. This will gracefully kill all the master processes, and will cause any running jobs (potentially on other nodes) to fail.
Equivalent to running
cryosparcm stop && cryosparcm start
Show a summary of how many jobs are active
Backs up cryoSPARC database. By default, creates a file in
cryosparc_master/run/db_backups/ with the current timestamp in its name.
To change the output location, specify the
cryosparcm backup \--dir=/path/to/backups \--file=custombackupfile
The cryoSPARC system maintains several log files for its various processes that help with debugging any components of the cryoSPARC system that are not working.
Shows the output log of the master node process denoted by
<process> which can be one of the following:
cryosparcm log command_core
The log is live and automatically updates while the command-line remains open and new data is added to the log. To stop live updates and return to the shell, press
control C on your keyboard, and then
To save the full log, redirect the output to a file
cryosparcm log command_core > command_core.log
To show only the last lines of the log, use
cryosparcm log command_core | tail -n 1000
This show the last 1000 lines of the log.
Shows a live output log for job
JXX in project
PX. Includes the standard input and error from the python process for the job.
For example, to show the output of Job 123 in Project 3, run the following
cryosparcm joblog P3 J123
To stop logging, save the full log or view only the last few log lines, see instructions for
Outputs a table of users registered with the system, including their names, email addresses and admin status.
Creates a new user account for log in through the web interface. Full use:
cryosparcm createuser \--email "<email address>" \--password "<new password>" \--username "<login username>" \--firstname "<given name>"\--lastname "<surname>"
Resets the password for indicated user with the new
<password> provided. Full use:
cryosparcm resetpassword \--email "<email address>" \--password "<new password>"
Updates a user profile to change the user name or set admin privileges. Full use:
cryosparcm updateuser \--email "<email address>" \--password "<current password>" \--name "<new name>" \--admin "<'true' or 'false'>"
--admin flags are optional.
Other than for the first-created user account, new users do not have administrative privileges applied by default. Following creation of the first-created user account, other accounts can also be created through the user interface if preferred:
Prints a list of environment variables for use in a command-line shell to replicate the exact environment used to when running cryoSPARC processes.
Run this command with
eval to define the variables output by the
eval $(cryosparcm env)
This may be used to, for example, run the Python distribution that ships with cryoSPARC.
Runs a command using with cryoSPARC's command-line interface
cryosparcm cli <command>
See the full command reference
Runs an an interactive cryosparc shell that connects to the master processes. Use this to interactively run Python commands in the same environment as cryoSPARC.
cryosparcm cli, but for running interactive commands with CryoSPARC Live.
Additional details coming soon.
Download test data (subset of 20 movies from the EMPIAR-10025 dataset) to the current working directory for use with the T20S Introductory Tutorial.
Prints a help message
mongo shell for cryoSPARC's local mongoDB instance.
Execute a shell command in cryoSPARC's shell environment, such as Python. Equivalent to calling
eval $(cryosparc env) followed by another shell command.