Open rdrighetto opened 1 year ago
Seconded, this would be very useful :)
Agreed. I am interested to know this.
Also expressing interest in this.
Hi all, the latest version of RELION (v5) actually uses 2D stacks of images, so should be compatible with the cryoDRGN-ET, with a little tinkering. I am thinking of writing a wrapper so the two are compatible but I need to clarify one thing:
In RELION v1.4 (which WARP/M uses), does anyone know where the rlnDefocusU/V values, which are read by cryoDRGN per-particle, are derived from? Are they simply the DefocusU/V values from the central tilt image of the tilt series stack during CTFFIND? Or are these values adjusted per-particle based on Z-height? Or something else entirely?
Hi all, the latest version of RELION (v5) actually uses 2D stacks of images, so should be compatible with the cryoDRGN-ET, with a little tinkering. I am thinking of writing a wrapper so the two are compatible but I need to clarify one thing:
In RELION v1.4 (which WARP/M uses), does anyone know where the rlnDefocusU/V values, which are read by cryoDRGN per-particle, are derived from? Are they simply the DefocusU/V values from the central tilt image of the tilt series stack during CTFFIND? Or are these values adjusted per-particle based on Z-height? Or something else entirely?
In early version of RELION, the rlnDefocusU/V seems to be calculated per particle based on <defocus at Z=0 +/- a shift (defined by their geometric Z location) >. I am not sure whether they will refine it later in 3D refinement, probably not.
Hi,
I am interested in trying tomoDRGN but I don't have Warp-generated stacks of tilts per subtomo for this dataset. So I have two questions:
tomograms.star
andparticles.star
files (i.e. an optimisation set)?Thank you!
Best wishes, Ricardo