CryoSPARC is designed around a master-worker pattern. The most intuitive use case, to me at least, would include long-running master processes with rare configuration changes. Other use cases are feasible, but would require special management.
I infer from your posts so far that in your specific case (please correct me as needed):
- CryoSPARC master processes are controlled by slurm. Please be aware that one should avoid sending
SIGKILLto CryoSPARC master processes like the database. - the CryoSPARC master host name and port (actually a range of consecutive ports) may change between shutdown and restart of a CryoSPARC instance.
- Are these assumptions correct?
- Do the data processing jobs initiated by the CryoSPARC master intended to run only on the same host as the CryoSPARC master processes (“single workstation” type instance), or are these data processing jobs individually submitted to slurm (see Clusters)?
In the example you showed, you may prepare CryoSPARC for a “session” with a modified port range by running the command
cryosparcm changeport 18883
assuming that ports 18883 through 18892 are not already in use.