It seems as though local refinement is ignoring user-supplied masking parameters in all iterations after the initial one (see screenshot below).
In this run, to exaggerate the effect, I have set the dynamic mask initial at 0 and the dynamic mask final at 20 Å. You can see that in the first (0th) iteration, the very fuzzy mask is correctly applied. In all subsequent iterations, the mask applied appears to be very sharp - almost binary, even though the dynamic mask sections look as one would expect given the supplied params.
The odd thing is, this is happening on one of my GPU workstations, but not the other, even though both have been updated to 2.14. On the GPU where it is an issue, varying the softness of the initial input mask has no effect - I still see these sharp mask edges in later iterations.
Thanks @apunjani - I don’t think it necessarily popped up in this version, I just noticed it now, when using very soft masking params. And actually I now see it on both my GPUs, but not for every dataset - if there is any info I can provide that would be helpful to debug, please let me know.
This bug is still present @apunjani - it really becomes a problem when using smaller masks. Have you been able to reproduce and/or identify the cause?
The weird thing is that when I download the refinement mask from that iteration it looks fine, but the masked volumes seem to have been masked with a binary mask (and show consequent ringing near the mask edges)…