Hi,
When I use local refinement, often it seems that the per-iteration changes in angles & shifts are larger than specified in the search range. Why is this?
Cheers
Oli
Hi @olibclarke!
The plot limits and search extent parameters differ for two reasons:
- The main reason is that these limits are set per dimension. So for example, for translation you’ve limited the search to 2 Å in both X and Y, meaning the greatest distance a particle can move is ~2.8 Å.
- The second reason is that we plot the shift in pixels, but the parameter is in Å. We agree this is confusing, so I’ve noted that we should make the plot also in Å.
3 Likes
Ah! That is very helpful, thanks @rposert!
not strictly related, but also confusing: when “use poses and shift gaussian prior” is toggled active, you can modify standard deviations of shifts/angles AND rots/shifts in degrees and angles. If you modify only the std dev. field, then shift/angles automatically populates (suggesting a calculation and update). But then what happens if you type into the rots/shifts? Which is used? I have long had the habit to set all of these values to ~4deg and 4ang, but now realize that likely by modifying the std deviations the protocol will ignore my rots/shifts and use a much larger value. Which could also cause the above confusion (why are my plots showing significant motion when I thought I limited to 4? - oh it’s because those values are ignored and it used 4 Std deviation which is 12ang and 12deg…)
But these are two different parameters - changing the range changes the total search range, changing the st dev changes the strength of the gaussian prior penalizing deviations from the initial values. The default is setting the range to 3x the st dev, but that is just a guideline - you can change it.
1 Like
One query about this @rposert - you mentioned the search ranges are per dimension - this also applies to the angles, presumably? So 2deg means 2degs in each of rot/tilt/psi, potentially?