read starfile puts everything in properties about blik HOT 6 CLOSED

I thought about this when doing it and actually disagree. I initially thought the same, but then I thought about the possibility of a GUI which lets you explore the relationships between properties of a set of particle blocks (does CC correlate with defocus, does class assignment correlate to tilt angle) so thought these things could be useful

from blik.

Ok, that's fine, but we should defnitely get rid of duplicate data, no? Is there any reason to keep shifts?

from blik.

from blik.

Ok, then we can keep it all! We should probably add some level of protection, to make sure none of these preexisting columns in the dataframe are overwritten by some arbitrary property by mistake

from blik.

from blik.

I think we can simply add a check on __setitem__ of the propertyblock that raises an error if you try to set those properties again? And we could hold a list of the properties created at instantiation, so only those ones are protected.

from blik.