At about 80min (7:16utc) into this current lock the ASC (mosty yaw) Oscillation began.  I got everything set up to run the command to change the phases (SDF window up to Accept changes, Observatory Mode to change mode, Intent Bit, AS36 window to watch phases, and a terminal to run the command).

From alogs, the most recent incarnation (alog 49116) of command to run that I found was:

z step H1:ASC-AS_A_RF36_SEG1_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG2_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG3_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG4_PHASE_R -1,28 -s 1

However, when I tried to run this step command, I received the following error:

corey.gray@zotws3:~$ z step H1:ASC-AS_A_RF36_SEG1_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG2_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG3_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG4_PHASE_R -1,28 -s 1
usage: step [-h] [-s time_step] [channel steps [channel steps ...]]
step: error: unrecognized arguments: -1,28 H1:ASC-AS_A_RF36_SEG2_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG3_PHASE_R -1,28 H1:ASC-AS_A_RF36_SEG4_PHASE_R -1,28

At first I thought it was a copy/paste issue, but no.  I'm guessing by the "unrecognized argument" it lists above, there is something wrong starting at the " -1", but that's a guess since I'm not familiar with this command (and I don't know where HELP about the "time_step" field resides).  I had run the previous command with no issues a couple of days ago; for comparison it was:

z step H1:ASC-AS_A_RF36_SEG1_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG2_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG3_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG4_PHASE_R +1,40 -s 1

I am stumped by the "[-s time_step]" because it looks like this should work!  The only difference between commands from last Thurs/today is the +/- signs.  Ugh!  Workaround thoughts (only thoughts):

• Could be a permission issue, so I logged in as controls, but had same error. 
• Try to run the command one quadrant at a time (but was scared to try that because maybe we want this change to happen to all quandrants in parallel, ASC world can be finicky).  
• Try running the original command from last week (but I assume we have this new command for a reason, so did not do this either)
• Wish we knew of a sandbox where I could play around with the step command to see what it does before running it on H1!

After the rough shift from last night while flying solo, and since the range/sensitivity has not taken a noticeable nosedive, I am deciding to live with our wiggly ASC/LSC signals with a ~2min period, and stay in OBSERVING.  If we have a lockloss, I will spend a few minutes tinkering around with this command to see what I'm missing.  If anyone reads this during my shift, and know what I'm missing, please give me a call to let me know what I'm missing so I can run it.  Apologies for not being able to run this.  I'm sure it's something basic. [Oh--I'm attaching a snapshot of where we currently stand with the AS36 R phases.]