I am proposing a model name change.  Currently, we have an "ASS" model, but we do not have an "ASC" model. 

The ASS is currently using ~17 of 60 available microseconds per cycle.  So, we have some cpu overhead available to put more stuff on that cpu. Like, say, ASC stuff.

So, my proposal is that we change the ASS model name to "ASC", and put all of the ASS-y things in a top_names block, so we retain the current channel names.  The IOO top_names block that is in the current ASS model (which is there to send signals to the LSC DAC for the input tip tilts, even though the names need to be IOO) should obviously stay on the top level, so that things in there retain their names.

Then, I can make a new top_names sub-block for ASC-like things, such as the new POP QPD. 

Inside the ASC block (in the ASC model), I'm currently thinking something simple will do..... QPD inputs, going to a matrix, which outputs to the filter banks in the "length" degree of freedom basis (PRCL, SRCL, etc), then another matrix, going to the ASC suspension paths. 

So, for example, the POP QPD pitch would go to the PRCL_PIT filter bank, and then on to the PRM_ASCPIT path in the SUS screen.

Or, in another example case, IPPOS yaw would go to an input pointing filter bank, then on to TT1's yaw slider.

EDIT:  After a few minutes of thinking, I think I also want triggering, and perhaps filter bank triggering, in the ASC model.  One of the reasons Koji has been pushing for the new automation system is that when the PRC fell out of lock, the ASC path would kick the PRM until Koji ran a down script.  Triggering will fix this issue, and it's the kind of thing that needs to happen quickly, so may not really be appropriate for the Guardian anyway.