Optics group missing?

[pconesa]

When importing an star file from an empiar deposition: https://ftp.ebi.ac.uk/empiar/world_availability/12098/data/EMD-50419_particles.star

Particle endsup with the acquisition.opticsGroupInfo filled... but without the _rlnOpticsGroup field with a 2 in this case.

Note that there is only 1 optics group with value = 2.

Using the assign opticts group protocol does not create the missing field either.

[azazellochg]

It looks like this has always been the case. You will have a _rlnOpticsGroup column in the particles table only if you have more than one group. Probably the reason was to limit the number of columns which is already very big. In any case, any join protocol will not deal with optics and they will have to be reassigned.

[azazellochg]

Let me know if you think this is something we need to add, it should be easy to do :)

[pconesa]

Then, at import time, the opticcGroup should be changed to 1. Those star files have only optics group 2. It's impossible to feed them to a 3d classification.

[pconesa]

Or, the assign optics group override existing optics group value in the acquisition.

[azazellochg]

Then, at import time, the opticcGroup should be changed to 1. Those star files have only optics group 2. It's impossible to feed them to a 3d classification.

oh, I see. I'll fix it