Upgrade v4 to v5

Install, Configure and Update
1

Hi team,

When updating from CryoSPARC v4 to v5, we noticed this:

" CryoSPARC v5 includes new database validation checks that ensure consistency. For this reason, when updating from v4 to v5, a database upgrade step will be automatically performed during the update process."

However, one of our use cases involves allowing our users to bind their existing database directories and configuration files in pre-built containers with different CryoSPARC versions. Consequently, users are able to go between versions without having to run cryosparcm update.

My questions are:

  • Is there another way to run this database validation done during the update?

  • Does this validation is run when starting CryoSPARC v5 with a database used in v4?

  • Will users have issues with starting v5 with an unaltered v4 database?

Kind regards and thanks!