@ 2:43 am (Local time) H1 called for assistance.
I noticed that it was a SQZ issue, specifically the SHG "PZT was out of range" error on the SQZ_SHG Guardian.
It was bouncing from Locking to Locked then scanning. etc.
I tried Init-ing SQZ_SHG manager..... SQZ_Manager.
Then I took all SQZ GRD Nodes to down except SQZ_PMC & SQZ_SHG and tried to troubleshoot the SQZ_SHG directly.
Looking at the SQZ troubleshooting guide: There wasn't a section for SQZ _SHG troubleshooting. So I searched the ALOG with no hits for "PZT Out of Range".
I tried to adjust the OPO temp to maximize H1:SQZ-CLF_REFL_RF6_ABS_OUTPUT. But changing the OPO temp had no impact.
This is when I started to realize it may take me awhile to find out what is going on, since it's too late to call a SQZ expert, I should just take us to NO-SQZ.
So I ran the noconda python switch_nom_sqz_states.py without script.
Sadly I did accept the SDFs and these too, because I thought they were causing an SDF issue. But it may have been SQZ_ANG_ADJUST needed to be at ADJUST_SQZ_AND_ADF instead of DOWN for the SQZr to be considered ready for OBSERVING.
Made it back to OBSERVING at 11:30:44 UTC
Now that we have made it back to OBSERVING albeit without SQZing I'm using a finer toofed comb on my troubleshooting.
I went looking for Sitemap>SQZ>SQZT0>SHG That last SHG Button was a bit difficult to find when your eyes are still crossed..
I then took a screenshot of the SHG screen before any changes.
I then locked the SQZ_PMC and the SQZ_SHG. The SQZ_SHG was cycling between locked and Unlocked. Dropped from Observing at 11:57:53 UTC.
Then while trying to maximize H1:SQZ-SHG_GR_DC_POWERMON I changed H1:SQZ-SHG_TEC_SETTEMP from 35.89 to 35.61.
After this I ran the noconda python switch_nom_sqz_states.py with script to try and get us the SQZ SQuoZe.
SQZ_MAN was having an issue with the SQZ_FC losing lock at Transition_IR_LOCKIN, I then re-touched up the OPO temp.
Success! The SQZr Is SQUOZE!!
Now I need to accept all the SDF's again (and these too ) cause I didn't follow the directions when i ran the initial no sqzing script.
Observing reached again at 12:51:32 UTC.
I edited SQZ_ANG_ADJUST which had a conditional, reading from sqzparams.use_sqz_angle_adjust, to set the nominal state (which stopped the script running correctly) to just stating the nominal state. Now there is a note in sqzparams.py to change the nominal state in SQZ_ANG_ADJUST and sqz/h1/scripts/switch_nom_sqz_states.py if the flag is changed.
Sheila, Camilla
This morning the SHG PZT was still around 5V so we changed the Offset, Min and Max scan rangers to force it to lock at the peak closer to 50V, see attached for old vs new values and sdfs accepted. Checked it scanned over the correct range by setting the SQZ_SHG guardian to DOWN and under manually scanning the SHG PZT.
Then I copied what Tony did last night and further optimized the SHG temperature to bring the power up from 96mW to 106mW, see attached. Thanks Tony!
