Guide: Updating to CryoSPARC v4

Installing or updating to CryoSPARC v4 is similar to previous versions of CryoSPARC, but downgrading is not possible past v3.4.0.

Upgrading from v3 to v4

All CryoSPARC projects, jobs and Live Sessions created in CryoSPARC v3 are forwards compatible with v4. You can upgrade an existing CryoSPARC v3 instance to CryoSPARC v4 using the same process outlined here Installing automatic updates

Because CryoSPARC v4.0+ relies on a newer version of MongoDB, after upgrading it will not be possible to downgrade to a CryoSPARC version below v3.4.0.

  1. cryosparcm update

This command will update to the latest version of CryoSPARC.

To update to a specific version, add e.g.,--version=v4.0.0

Downgrading from v4

CryoSPARC v4.0+ relies on a newer version of MongoDB, v3.6, than CryoSPARC v3.3, which relies on MongoDB 3.4. Therefore, after upgrading to CryoSPARC v4.0, it will no longer be possible to downgrade to a version of CryoSPARC that relies on a version of MongoDB older than v3.6.

CryoSPARC v3.4.0 was created to allow downgrades from a v4 version of CryoSPARC to a v3 version, where necessary. CryoSPARC v3.4.0 is a carbon copy of CryoSPARC v3.3.2+220824, the most recent pre-v4.0 release of CryoSPARC, and includes support for MongoDB v3.6. It is possible to update to CryoSPARC v4.0 from v3.4.

  1. Follow downgrade instructions from the guide and specify: --version=v3.4.0

Application & Port Changes

The new web application replaces the legacy web application at the main (base) port of your CryoSPARC instance. In v4+, the legacy web application is not started by default during cryosparcm start, but can be turned on by running cryosparcm start app_legacy.

You can still access the legacy web application via these ports:

ApplicationPort Number

New application

BASE_PORT (e.g 39000)

Legacy application

BASE_PORT + 7 (e.g. 39007)

Last updated