ETMY L1 noisemons unsafe for loud triggers

Paraphrasing from Slack:

We should add the ETMY L1 noisemons to the unsafe channel list for GravitySpy hveto runs and future hveto runs. We don't have loud enough injections to see it for sure and the stats for hveto safety are marginal, but Andy showed that it's likely things with DARM SNR > 50 are seen by these.

andy [3:38 AM Dec 5 2017] ok, yep, so it's vetoing on low-Q things And I've found that the noisemon appears in hVeto on July 27th https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170627/detchar/hveto/ didn't see it at all for days before that time, then see it all the time and it vetoes nearly everything above SNR 100 could just be picking up DARM feedback, but I don't see how it suddenly became so much more sensitive

andy [5:40 AM Dec 5 2017] Yep, the noisemon channel came alive after they fixed the IMON: https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=180778 all four quadrants suddenly have something in them

joshua.smith [10:48 AM Dec 5 2017] @andy The H1 detchar safety injections were done on Aug 26 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=38380 . Thomas Abbott's hveto safety studies list the ETMY L1 Noisemons as marginally unsafe (the cutoff is significance=2) at that time: https://ldas-jobs.ligo-wa.caltech.edu/~tabbott/HvetoSafety/H1/O2/safetyinjections/D20170826/results/H1-HVETO_omicron_omicron-1187823990-1925/safety_6.html They "veto" ~30 of the ~130 injections, but have 1500-2500 triggers in the veto, so very low use percentage ~30/2000=1.5%, and the Ncoinc/Nexpected by chance is about 1.7.

The channels we will add to the unsafe list are:

%(IFO)s:SUS-ETMY_L1_NOISEMON_UL_DQ

%(IFO)s:SUS-ETMY_L1_NOISEMON_UR_DQ

%(IFO)s:SUS-ETMY_L1_NOISEMON_LL_DQ

%(IFO)s:SUS-ETMY_L1_NOISEMON_LR_DQ