While carrying out class averaging for particles I encountered " illegal memory access was encountered". I do not find a solution to overcome this. Additionally this happened when I am trying to add another set of data to the existing one (which already provided a 3.4 Å resolution map).
Any feedback and a fix to the problem will be helpful.
@Andy Please can you add more details about the error:
cryoSPARC job type
where in the logs or interface the error was encountered, with additional lines of output for context
the current “physical” box size of the particle stacks and any job parameters that affect the job’s memory complexity (resolution, number of classes, particles, etc.)
hardware and software:
how the other dataset was added to the existing one, and how the datasets differ
The above issue also taken care of at present (BUT I will revisit it later to provide you more details). I have another problem.
I recently completely a helical reconstruction with resolution up to 3.6Å. Now I want to generate the whole 3.6Å map to a much larger length (it is a phage tail density map). I will need the asymmetric map (at 3.6Å) so that I can symmetrize it to generate a 1200Å long map (the map is ~256Å long). How to obtain the asymmetric map ?
Is there any alternate way to do it ?
I want to sort out heterogeneity based on the Pitch of the helix. I can generate maps for classifications from the asymmetric map, requested above. Following that How to I carry out the classification using the maps in cryosparc ?
I binned the images in BSOFT (or you can do it in any package like EMAN2) and then imported them in Cryosparc.
However if memory serves well, there should be an option in cryosparc, I can possibly reply you back tomorrow or day after tomorrow. Some one from cryosparc team can definitely reply you, sooner but you can try the ‘Fourier crop to box size’.
Depending on your stage of the workflow, “binning” can be accomplished in various job types.
For example, see this discussion about Patch Motion Correction.
Additionally, there are the Extract From Micrographs and Downsample Particles job types that can achieve a binning effect.
I’m running the Topaz Extract job, but it errored “out of memory”. I thought if I can bin the micrograph in a separate job, then do the Topaz extract, this error may cleared.
Hi @CleoShen - the defaults for topaz extract are quite memory hungry - you might try reducing the number of threads and processes, if you haven’t already.
Thank you for your reply.
I binned the micrographs by Patch Motion Cor Job, then the Topaz Extract works, but I would like to downsample more, such as bin8, bin16, but the CS Patch Motion Cor F-crop option only provides as many as bin4, if you know how can I downsample more in CS?
This shouldn’t be necessary to run Topaz, as Topaz downsamples on the fly. Have you tried adjusting the downsampling factor in Topaz? What settings are you using?
@olibclarke@wtempel
I am taking this thread to ask about the helical processing questions that I have posted 2 months ago ? I think a separate thread is made but have not received any response. Can you help.