Import particles between projects

[Jared]

Sorry if this topic was asked about before.

I’m trying to export the particles from one project to another project. Same protein, just the data was collected on different days.

I used the export button under the heterorefinement to export the particles from project 1, then I tried using import results group to import the .csg file that was generated into the second project. However I get the error that this wont work because they arent part of the same project. What is the best way to do this?

[wtempel]

Welcome to the forum @Jared. Please can you paster the text of the error message.
In case the message was

Result group to import must be located inside the project directory

I should clarify that the file(s) to be imported must reside inside the destination project’s directory (see related topic Import result group problems). One way of accomplishing this is to

1. ensure the destination project directory contains a imports/groups directory
2. copy or link the relevant subfolder inside the exports/groups directory of the source project’s directory to the imports/groups/ directory inside the destination project directory

[CryoEM2]

yep, they can still have the old Pxx project name, this one result folder just has to be moved to the new Project folder location, then can be imported.

[Jared]

Copying the export of the first project into the import of the new project and running the import results group on the data worked. Thank you!

[JuenZhang]

I have a large dataset. The exported job contains the motion corrected micrographs and other files. Tar, and copy the files just takes forever. It will be great if we can directly import jobs for other project’s export folder.

[CryoEM2]

a cp would be slow, but a mv would be immediate, no? this was 2 years ago, perhaps there is some development in the process by the cryosparc team

[olibclarke]

See here:

Moving a particle stack to a separate machine

The problem is that when exporting a job, all the prior “dependencies” in the workflow are exported too. The solution is to first get rid of these by inputting your extract micrographs job (for example) into a particle sets job (setting the batchsize to an arbitrarily large value), and removing the location slot from the expanded inputs (which will remove the micrographs from the outputs). Now when you import the job using your first described method, it should just copy across the particle st…

For a way to just copy the particles, without associated micrographs. Of course if this is on the same machine, you don’t need to physically copy the exported folder, you can just symlink it to the imports dir of the other project.

[wtempel]

@JuenZhang

Tar, and copy the files just takes forever. It will be great if we can directly import jobs for other project’s export folder.

If the source project directory is and will be available on all nodes of the destination instance, you may create a symbolic link to the exported job folder inside the destination project directory.

[MD25]

Hello,

I am trying to combine the extracted micrographs from three datasets of same sample just collected on different days.

First I exported the extract micrograph block of each project and checked that the export folder generated, then created the import result group only inside the same project because it didn’t allow me to import result outside the project.

After that I am unable to combine them in a new workspace in one of the project.

[CryoEM2]

do you mean extracted particles?

you have to move/copy/link the raw data into the same project architecture where you want to access it. outside of cryosparc, in your file manager. then you can use cryosparc to import and combine.