Dear Fabian,
Thanks for your amazing work and we found paceTOMO super helpful with our cryo-ET data collection pipeline. We tried to set up the newest version of paceTOMO and serialEM on Titan and encountered some issues during realignToItem.
Environment
- paceTOMO version: v1.9.2
- SerialEM version: SerialEM Version 4.2.1 64-bit, built May 19 2025
- Microscope / camera: Titan Krios G4 and Falcon 4
- OS: Windows
Summary
When using paceTOMO's realignToItem function in the new version, the acquired view magnification reference shows a fixed positional offset equal to the serialEM tilt axis offset. We had to manually move our target back to the original position when finalizing the targert, and the result appears to cancel the tilt-axis offset during collection and produces tilt-series with a large defocus slope. Using SerialEM's native realignToItem function does not produce this problem, but it is less robust since we rely more on the focusing area to align back all targets. We wonder whether this could be a bug in paceTOMO communicating with the updated version of serialEM, or is it more likely caused by our SerialEM configuration?
Best,
Siyu Chen
Dear Fabian,
Thanks for your amazing work and we found paceTOMO super helpful with our cryo-ET data collection pipeline. We tried to set up the newest version of paceTOMO and serialEM on Titan and encountered some issues during realignToItem.
Environment
Summary
When using paceTOMO's realignToItem function in the new version, the acquired view magnification reference shows a fixed positional offset equal to the serialEM tilt axis offset. We had to manually move our target back to the original position when finalizing the targert, and the result appears to cancel the tilt-axis offset during collection and produces tilt-series with a large defocus slope. Using SerialEM's native realignToItem function does not produce this problem, but it is less robust since we rely more on the focusing area to align back all targets. We wonder whether this could be a bug in paceTOMO communicating with the updated version of serialEM, or is it more likely caused by our SerialEM configuration?
Best,
Siyu Chen