hello @leetleyang , perhaps you right. I tried different pixel sizes for the output map but with the same results (in my case). What may also be important is the decimal number after 0 to be even…not sure
I’m a bit unclear on how the Resample to box size feature works.
Crop to box size is straightforward – it involves specifying a desired box size without affecting the pixel size, operating in real space.
However, Resample to box size is causing some confusion. My understanding is that changing the pixel size involves adjusting parameters in Fourier space.
Through some experimentation, I’ve identified the following values:
240px results in 1.065 A/pix
360px results in 0.71 A/pix
384px results in 0.66563 A/pix
I’ve found that 350px at 0.73029 A/pix is what I’m aiming for.
However, I suspect there might be a more elegant way to determine these parameters.
In some software, there’s a window where you can specify the final pixel size, which might be what led to my confusion.
Any insights or guidance would be much appreciated.
Resample to box size expects box_size[output] in units of pixels as its input parameter. If performing resampling and cropping in the same job, cropping occurs after the resampling operation, so you’ll have to think about this in terms of the resultant resampled box/voxel size.
Generating the desired box/voxel size may require some degree of padding or cropping of the input map, prior to resampling. However, often you can’t get them close enough for cryoSPARC to not complain. In which case once you’ve gotten it as close as you can, you can then fudge it by reimporting the volume and overriding the voxel size to match.
Whether this is appropriate or not depends on what you intend to do with the volume and whether it requires that additional degree of precision.