Before detaching a project became robust we were locally recommended to archive projects and back them up. However since then our database was pruned to remove older archived projects. I would like to revisit one such project. It was created in an older cryosparc version (likely pre 3.x).
Can an archived project be imported into a different cryosparc instance? If so what needs to be done? I guess workspace and project json files would be missing or need updating.
Best,
Joe
with archived project you are not referring to the CryoSPARC Archive Project function, which only became available in CryoSPARC v4, but to copying the project directory to archive storage.
the project directory has been recalled/restored from archive storage
the restored project directory is not accessible to any CryoSPARC instance where the current project directory path may coincide with the project directory path of a preexisting CryoSPARC project on that CryoSPARC instance
you may try attaching the restored project directory to the CryoSPARC instance.
The assumptions above are meant to ensure that no more than one CryoSPARC instance interacts with the project directory. The project lock should protect against concurrent control of a project directory, which would corrupt the project directory, by multiple CryoSPARC v4+ instances, but no such protection exists against interference by a pre-v4 CryoSPARC instance. Please let us know if you have any questions.
Both instances 1 and 2 are running cryoSPARC 4.6. There were some jobs deleted in instance 1 but not the ones that were ancestor to the later jobs. The strange thing is that after I reattached the project in instance 2 some jobs and connections do not appear in the tree view but all the jobs do appear in the card view and selecting the ancestor jobs in the card view also appears to properly select all related ancestor jobs.