In investigating the cause of the peak at 102Hz (72064, 72108), the cause had been narrowed down in between a calibration lines issue or an LSC FF issue. Since the change to the LSCFF ramp times did not fix the peak (72188), Jeff and Ryan S added a new ISC_LOCK state today(well 8/14 22:45UTC) (72205), TURN_ON_CALIBRATION_LINES, so that the calibration lines aren't turned on until late in the locking process.

In the following locking sequence (72201), the peak still appeared around the LOWNOISE_LENGTH_CONTROL and TURN_ON_CALIBRATION_LINES states, so it was decided that the next time we lost lock, we would pause on the way back up at LOWNOISE_LENGTH_CONTROL to determine which of the two states the peak was linked to.

We lost lock at 2:09UTC (72209), so I set the detector to only go through to the state right before LOWNOISE_LENGTH_CONTROL (I selected LOWNOISE_ESD_ETMY when it should've been LOWNOISE_ESD_ETMX but that presumeably wouldn't which of the two states the peak turned on at), and then selected LOWNOISE_LENGTH_CONTROL and the 102Hz peak appeared quickly after (full spectrum, zoomed in). Once we had been in that state for a bit I moved to TURN_ON_CALIBRATION_LINES to see if that would cause the peak to change in any way, but it didn't change(zoomed in - not the best ss sorry). So the peak at 102Hz is caused by one of the filter gains in LOWNOISE_LENGTH_CONTROL.