Ricardo Righetto

Is it consistently happening for you, or is it random? I run into this issue randomly on our cluster, so I assume just a glitch in network communication, but not...

Just writing here to express that we cannot wait for cryoDRGN-ET to support data generated by WarpTools and RELION-5 😃 Just a heads up that particle STAR files generated by...

Just wanted to share that I've also had this issue. I got it to work by forcing my .mdoc and .eer files to share the same rootname by renaming symlinks....

You should say "Yes" to the "Use GPU acceleration?" in the "Compute" tab of your job, which will specify the `--gpu` command line option in order to use the GPUs...

Hi @lmcarreira, You need to make sure that you have AreTomo installed and that the binary is available in your `PATH` environment variable before launching RELION, as suggested by the...

Are you submitting the job to a cluster e.g. with SLURM? If so, you have to make sure that the AreTomo module (or `PATH`) is properly loaded in the submission...

Hi @lmcarreira, First thing to keep in mind is that `tomograms.star` files made for RELION-4 will not work with RELION-5 (what I intended to do in my original post). Many...

Hi @ShelvinZhang, As it is currently implemented, the RELION-5 wrapper for AreTomo does read the tilt angle offset determined by that program, but the same is not true for the...

Just confirmed that `relion_tomo_reconstruct_tomogram_mpi` works again when reverting to 6331fe600cca7683ecf7c1011ce676701faf1e97 with exactly the same settings.

Another update: using the latest 96f798eb8a7eafa7e6d27c8b32711aad701cdfa2 on branch `ver5.0`, `relion_tomo_reconstruct_tomogram_mpi` works as before if I say NO to "Fourier inversion with odd/even frames?", but crashes with the error above if...