D. Barker, J. Kissel, N. Patel, E. von Ries
WP #9871

Dave, Erik, Nidhi, and I worked through installing and running the two new front-end models, h1susifoout and h1sussqzout, today. The design of these models is covered in LHO aLOG 59651, this aLOG covers what surrounding infrastructure needed to be changed in order to support the new models. In short:
   - we've got all models that cover still-existing suspensions -- SR3, SRM, the OFI, the OMC, and OMs 1-3 -- back up and running, all settings and filters restored, and we've done a precursory check that they're safely damped and happy.
   - the model covering the new suspensions -- ZM4, ZM5, ZM6 -- is installed, and has supporting infrastructure but it's empty, to be filled in at a (soon) later date.

Here were the steps: 
   - Made sure that both top-level models where committed to the userapps svn
   - Dave found and fixed the bugs in my design, and/or the things that were preventing compilation, including
        - changing the name of CDS block parameter variable "site" to "ifo" as per new protocol from RCG 4.01
        - Removed any receiving IPC from h1sussqzout that didn't have any senders
        - Fixed a bug in the replica OMC SUS WD connection in the ISI HAM6 model (I'd misinterpreted the logic in the PAYLOAD block)
   - I brought down all HAM5 and HAM6 SUS and ISIs to SAFE and ISI_OFFLINE_HEPI_ON, respectively
   - Dave/Erik brought the HAM56 models out of the dolphin network
   - Erik restarted the h1isiham6 model to pick up the IPC sender change
   - Dave/Erik removed the old h1susomc and h1susopo models from (somewhere something ... maybe the DAQ .ini file? )
   - Dave/Erik installed the new h1susifoout and h1sussqzout into the (somewhere something ...)
   - Dave/Erik started the models, and we found the the existing SUS in h1susifoout came up, but with no filters and all the default RCG settings for EPICs values. Reminded that we need supporting safe.snaps and foton filter files for even the old suspensions, because they live in a new model name, and burts and foton files are named after the *model*.
   - Jeff created the burt snap file (and committed to the repo)
        /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susifoout_observe.snap
     starting from a verbatim copy the h1susomc_observe.snap and then hand-copying in every OFI setting from the h1susopo_safe.snap
   - Jeff created the foton file (and committed to the repo)
        /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSIFOOUT.txt
     starting from a verbatim copy of the H1SUSOMC.txt, and then hand-copying in every OFI header information and filter from H1SUSOPO.txt
   - Dave created the softlinks to the above mentioned burt file in
        /opt/rtcds/lho/h1/target/h1susifoout/h1susifooutepics/burt/
              OBSERVE.snap > /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susifoout_observe.snap 
              safe.snap > /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susifoout_observe.snap
   - Dave created softlinks to the above mentioned foton file in 
        /opt/rtcds/lho/h1/chans        
              H1SUSIFOOUT.txt -> /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSIFOOUT.txt
   - Erik recompiled, re-installed, and restarted the h1susifoout model, and all existing SUS came up as expected.
   - Nidhi and I slowly, but surely brought all existing HAM56 SUS and ISIs back online, untripping watchdogs, using guardian to head back to ALIGNED. Success!
   - Nidhi and I brought all the SUS *back* to safe, now including SRM and SR3 
   - Erik then tested the auto-restart process of the whole h1sush56 computer.
   - Medium success:
        - All models came back normal, as expected, with all settings intact.
        - Erik/Dave will aLOG that there was another instance of the known bug that taking out any model from the dolphin network for an extended period of time causes the H1 OAF computer to ... "burp?" ... and then take down the Data Acquisition / Frame Writer system)
   - Nidhi and I brought all the HAM56 SUS and ISIs *back* to fully functional, now including SRM and SR3.


There's still *PLENTY* of work to do with the ZM4-6 infrastructure, but that'll be for another day.