The parameter 'maxsig' for thresholding output ratemaps is providing user confusion, since if it is set too low the resulting output products are blank or very sparse. Based on this, we should move the application of maxsig to the ‘merge’ step, so that by re-running ‘merge’, you can quickly try different thresholds without having to re-run the full 'process' step.
In addition, here are a few options (increasing complexity):
Discard maxsig completely (user can threshold themselves during post-processing).
Give a screen message that describes the proportion of pixels that have been masked by the chosen maxsig threshold.
Automatically estimate a reasonable maxsig threshold from the data set (several options to do that, e.g. using percentages or a histogram fit).
2 and 3 could be somehow combined by having maxsig set to ‘auto’ by default in the config file, but still allowing the user to manually set a value if need be.
The parameter 'maxsig' for thresholding output ratemaps is providing user confusion, since if it is set too low the resulting output products are blank or very sparse. Based on this, we should move the application of maxsig to the ‘merge’ step, so that by re-running ‘merge’, you can quickly try different thresholds without having to re-run the full 'process' step.
In addition, here are a few options (increasing complexity):
2 and 3 could be somehow combined by having maxsig set to ‘auto’ by default in the config file, but still allowing the user to manually set a value if need be.