Yannick Lecoeuche authored 4 years ago and Jameson Rollins committed 4 years ago

This adds an additional plot to the summary page that indicates which suspensions tend to saturate with each other. The 1st suspension to saturate in a lockloss goes on the y-axis, and the 2nd-5th saturating suspensions go on the x-axis. The code only looks at suspensions that saturated before the refined lockloss time and does not allow repeats (that come from UR, UL, LR, LL).

Closes #126

See merge request jameson.rollins/locklost!96

Yannick Lecoeuche authored 4 years ago and Jameson Rollins committed 4 years ago

Fixes the shift check in the summary code by assigning timezones for LHO and LLO. Also cleans up a large portion of code with defaultdicts, for-else statements, and any other improvements I could think to make.

Improve zoomed refine plots

See merge request jameson.rollins/locklost!99

Yannick Lecoeuche authored 4 years ago and Jameson Rollins committed 4 years ago

As mentioned in #161, when a zoomed refined time plot has a threshold crossing outside of the plot window, the channel data outside the window does not get plotted. This is because the code is specifically selecting data that falls within the window. This code plots all the data and chooses xlims based on the refined time and window boundaries.

This generally shouldn't be necessary, as we don't expect good refinement to yield times more than 5 seconds before the unrefined lockloss time, but it's nice to have consistent plots.

Adding check for fast LOCKLOSS_DRMI -> ACQUIRE_DRMI_1F -> LOCKLOSS transitions

Closes #109 and #150

See merge request jameson.rollins/locklost!91

Yannick Lecoeuche authored 4 years ago and Jameson Rollins committed 4 years ago

Add logic to the history plugin to check if ISC_LOCK_STATE went from the lockloss state we're interested in (generally between 103-202) to LOCKLOSS_DRMI (3), then up briefly to ACQUIRE_DRMI_1F (101) before LOCKLOSS (2). In order to create the refined time plot correctly, the history followup moved before the refine followup in execution order. Additionally, I added a setter to change transition_index to the new values (I also removed the assertions, because they would cause an error whenever this condition was met).  This is only for H1.

Closes #150

Search for and tag FSS oscillations before lockloss

Closes #109 and #154

See merge request jameson.rollins/locklost!94

Yannick Lecoeuche authored 4 years ago and Jameson Rollins committed 4 years ago

Look at PSL-FSS_TPD_DC_OUT_DQ for dips below 0.3 within 5 seconds before lockloss and creates tag if it finds any. These FSS-related locklosses are fast, and the glitch is expected to occur very close to the refined lockloss time. For this reason it depends on a strong lockloss refinement, which may preclude LLO from getting good use of this followup.

Check and tag if Observatory mode is Commissioning or Maintenance

Closes #109 and #121

See merge request !95

Split up refine_time into two functions so the calculation can be called separately

Closes #159

See merge request !97

Camilla Compton authored 4 years ago and Jameson Rollins committed 4 years ago

This is mainly a copy/paste to split the refine.py function refine_time into two functions:

* find_transition: Takes an input of the time window and dictionary containing information about the channel needed for refinement (channel, std, min); then outputs the threshold used and refined time.
* refine_time: Does the job of the old refine_time function but calls new find_transition function to do the actual refinement calculation.

The reason for this change is that in the future I would like add a plugin to look at speed or order of light falling off PDs. This plugin could then call the function refine_calculate rather than copy/pasting refinement code.

Only change made to logic is on lines 58-60, where now if the refinement has already been done, the previously refined time will be used to center the search window rather than the transition_gps. This will not make a difference for the normal refinement but should speed up future plugins that use the refinement calculation as the search window could be smaller.

Closes #159

until issues resolved

Mostly PEP8, and drop use of LAL, but also fix some issues with directory
creation.

Seismic dev branch

See merge request !89

Marc Lormand authored 4 years ago and Jameson Rollins committed 4 years ago

Expand SEISMIC tag into separate tags indicated elevated noise in the separate EARTHQUAKE, ANTHROPOGENIC, and MICROSEISMIC bands; include plots for all bands.

Adding lockloss summary plots to webpages

Creates a new webpage with link (in green) located below the github links. Adds a module (locklost/summary.py) that collects data from EVENT_ROOT and creates/saves histogram plots based on this data. These plots are saved to a directory (events/summary_plots), which is further subdivided into directories for plots derived from locklosses in the prior week, month, and over the entire run (ex: events/summary_plots/Month).

The ability to run the summary module from the command line is added to locklost/__main__.py, and the summary plot template is added as locklost/web/templates/summary.tpl.

See merge request !93

Yannick Lecoeuche authored 5 years ago and Jameson Rollins committed 5 years ago

Closes #109 (closed)

Tag locklosses that occur while SEI_BS is transitioning

Closes #149

See merge request !92

Yannick Lecoeuche authored 5 years ago and Jameson Rollins committed 5 years ago

Checks three seconds before lockloss to see if SEI_BS was in the transitional state (-19), and tags it if that is the case. I have been assured by Jim that the SEI_BS Guardian has not been changed in several years and will not be changed in a way that would alter the -19 designation. If this is still a concern I can request the state to be assigned a permanent number.

Skips if IFO == LLO because, as far as I know, they are not having the same BS stage 2 transition locklosses that we are.

Closes #149

CondorError exception doesn't exit, use RuntimeError instead.

Cleanup BRS glitch code

See merge request !88

Yannick Lecoeuche authored 5 years ago and Jameson Rollins committed 5 years ago

After the string of rebases/messy reverts/etc on my local repository, there were some artifacts leftover in the recently merged code (which checks if a BRS is in use before analyzing it for glitches).

This should fix those issues by:
* Removing the variable print/second collapsible plot on the website
* Creating a title for the BRS section if no BRSs are being used
* Fix channel name creation
* Delete state channel after use (so it isn't checked with BRS values)

Add lpy coefficients for OM's, RM's, ZM's

Closes #130

See merge request !90

Also add some additional tests.

* move online_status into main
* remove unnecessary event_summary function
* remove other superfulous code

to unify how events are generated from query