You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New runs of VET have glitchgrams (Omicron plots) in which high SNR points are plotted first, followed by low SNR points, so the low SNR points obscure any high SNR points under them. This is a known issue which is discussed here: "Change in formatting of Omicron plots in summary pages" - https://git.ligo.org/detchar/ligo-summary-pages/-/issues/171 . Investigation has not turned up the exact cause of the change in plotting order (which is detailed on the above LIGO Summary Page issue), but a GWpy fix has been submitted in a pull request ("Handle changes in kwarg defaults in Axes.scatter (take 2)" - gwpy/gwsumm#333 ), which is awaiting approval. Some work is also being done to determine exactly what software change (probably in a Conda environment) caused the change in plotting behavior.
The text was updated successfully, but these errors were encountered:
Note that in order to plot higher SNR points on top of lower SNR points, the updated code requires the config file to include "glitchgram-sortbycolor = True" in the "[DEFAULT]" section (e.g., here).
New runs of VET have glitchgrams (Omicron plots) in which high SNR points are plotted first, followed by low SNR points, so the low SNR points obscure any high SNR points under them. This is a known issue which is discussed here: "Change in formatting of Omicron plots in summary pages" - https://git.ligo.org/detchar/ligo-summary-pages/-/issues/171 . Investigation has not turned up the exact cause of the change in plotting order (which is detailed on the above LIGO Summary Page issue), but a GWpy fix has been submitted in a pull request ("Handle changes in kwarg defaults in Axes.scatter (take 2)" - gwpy/gwsumm#333 ), which is awaiting approval. Some work is also being done to determine exactly what software change (probably in a Conda environment) caused the change in plotting behavior.
The text was updated successfully, but these errors were encountered: