tskisner
commented
1 year ago In response to "Should we enforce somehow that all operators respect the new detector flags?", although all operators do not explicitly check these, there is now an option to the select_local_detectors() method (which IS used by most operators), which by default excludes detectors with the invalid or processing mask bits set.
This was a compromise to make things work transparently in most cases for the existing operators.
Add a new operator (AzimuthIntervals) which uses smoothed versions of the azimuth velocity and acceleration to detect azimuth scan patterns and define the typical intervals.
Add support for per-detector flags that apply to an entire observation. These can be set / updated and use the same masks as per-sample detector flags. These flags can now be used to optionally control selection of local detectors for processing.
Add new operator (FlagNoiseFit) which uses the analytic fit to the noise estimate to flag detectors for an observation. The current implementation can flag outliers in both the estimated NET and knee frequency values.
Visualization: small fixes to ipython widget and improvements to WCS and noise estimation plotting functions.
Set the SimGround bitmask to enable turnarounds in the unit tests
Allow optionally running with a single process group in the unit tests, even if using >= 2 processes.
Pull out duplicate code to compute the detector scan range for and observation. Use this common function in atmosphere simulation and WCS projection autoscaling.
When fitting an analytic 1/f model to estimated noise PSDs, allow overriding the frequency range that is considered the white noise plateau.