GUI: Better handling of mosaicity
Mosaicity is taken into account when assigning shapes to predicted peaks via ShapeCollectionDialog
; in other codes it is part of the prediction process and its effect is immediately obvious. It affects the extent of peak shapes, i.e. a high mosaicity causes peaks to extend over more frames, resulting in more peaks per frame. After predicting peaks, they are assigned a default shape, so the mosaicity is necessarily incorrect and misleading.
- It should be possible to assign shapes directly after prediction, rather than before integration
- It should be possible to control the mosaicity and see its effect directly on the
DetectorScene
.