Alternative suspension models
For ET (and Virgo), we will want to include a different or at least modified suspension model. It is not completely clear to me how we could go about that. There is currently an (unused)
ifo.Suspension.Type parameter in most of the YAML files. It seems natural to use this in
precomp_suspension to call the appropriate code, instead of always calling
suspQuad. Unsure where the code then would live, however. Adding it to
suspension.py seems too much, but if it lives in a different file, we might need some additional glue logic to import the correct file. This may be overthinking it, however... it's unlikely we'll have that many models. Also, is the function's signature how we want it and should we use this to make other models take exactly the same parameters and return the same TFs? Are there any other places that need to be adapted? The functions in
suspensionthermal.py may actually be general enough to be reused, however the names of individual contributions in
SuspensionThermalHorizAPM) are "quad-centric".