J. Kissel, D. Barker

After Dan made changes to the OMC's ASC scheme (LHo aLOG 17325), and Dave subsequently restarted the h1asc front-end model this morning (I don't know why, hopefully an aLOG is pending by the author of the change, maybe to do with WP #5112), which uncovered a flaw in the new OM3 IPC receiver connections. T'was a simple copy-and-paste bug in the channel naming, so I just went ahead and fixed it. We await a DAQ restart to close out the work.

Details:
Attached are before vs. after screen shots. Forgive the terrible Simulink vs. Ubuntu graphics rendering, but the bug was in the OM3 stuff at the bottom, so the bad rendering doesn't affect my demonstration. Dan was presumably copying and pasting the OM1 / OM2 IPC senders, and forgot to remove the simulink-added "1" and "2" to the end of the name.

Before restarting the model, I updated the h1sushtts SDF file, seeing that the majority of the changes were alignment offsets and corresponding tramps. I presume the alignment settings are good, given the Megaparsec report from last night (see LHO aLOG 17411).

After restarting the model, I've committed the latest version of the model and the SDF capture to the userapps repo.