Merge branch 'master' into blm_checks

Author: fsoubelet

docs/guis/betabeat/betabeatsource.md

@@ -6,9 +6,9 @@ and is no longer under active development.
 
 Legacy version are still available on [CAS][bbs_cas]{target=_blank .cern_internal}.
 
-## Meaning of the Output Files
+## Meaning of the Beta-Beat.src Output Files
 
-The naming of output files in Beta-Beat.src analysis can be very unintuitive.
+The naming of output files in legacy Beta-Beat.src analysis can be very unintuitive.
 Namely, one will see similar output files for a quantity which go as `get_*.out`, `get_*_free.out` and `get_*_free2.out`, where `*` is the calculated quantity (betas, phase, etc.).
 These each correspond to a variation of the calculated quantity, explained below.
 
@@ -18,13 +18,14 @@ One can compensate for this deviation in different ways, which is why there are
 
 !!! example "Meaning of Different Output Files"
     | Nomenclature      | Meaning                                                                                                        |
-    | :---------------- | :------------------------------------------------------------------------------------------------------------- |
+    |:------------------|:---------------------------------------------------------------------------------------------------------------|
     | `get_*.out`       | The optics functions **without** compensation, from the driven excitation data.                                |
     | `get_*_free.out`  | The optics functions compensated **analytically** using an equation[^MiyamotoMeasurementCouplingRDTsACDipole]. |
-    | `get_*_free2.out` | The optics functions compensated **the other way**, see below.                                                |
+    | `get_*_free2.out` | The optics functions compensated **the other way**, see below.                                                 |
 
-    In the case of the `get_*_free2.out` files, the compensation is done differently depending on the computed quantity.
-    For some quantities (for instance for $\beta$ from phase) this uses the model values, for others (for instance the coupling RDTs $f_{1001}$ and $f_{1010}$) it is a rescaling in which the model values are used *indirectly*.
+    In the case of the `get_*_free2.out` files, the compensation is done differently **depending on the computed quantity**.
+    For some quantities (for instance for $\beta$ from phase) this uses the model values.
+    For others (for instance the $f_{1001}$ and $f_{1010}$ coupling RDTs) it is a rescaling in which the model values are used *indirectly*.
 
 The method used to output the `get_*_free2.out` files is sometimes more robust as it does not rely on the existence of certain BPMs in the output (which could be missing after cleaning), and in some edge cases is more accurate[^HoydalsvikSubPerMilCouplingLHC].