--- Ring Object === ### Usage in codes other than tracking <!-- .slide: class="center" --> --- ## For data analysis <img src="https://codimd.web.cern.ch/uploads/upload_a10f43370c49463e440d75d6f0399e00.png" width="60%"> - Acquisition is based on triggers on $f_\mathrm{rev}$ clock. Usually need to recompute $f_\mathrm{rev}$ to get the distance between two frames. --- ## For data analysis <img src="https://codimd.web.cern.ch/uploads/upload_5f73aa715efb44fc30e54d7560c877c6.png" width="60%"> - This can be used to get the bunch spacing for easier bunch detection - **What is needed:** Mostly to get $\beta$, $\gamma$, $t_\mathrm{rev}$. Programs are necessary if these parameters change a lot (e.g. measurements along the ramp) --- ## For the impedance toolbox <img src="https://codimd.web.cern.ch/uploads/upload_782480cf19c526dc1005c5a20ff56058.png" width="60%"> - The Ring (and RFStation) object(s) are wrapped into a Machine object - Transparent for the user, based on known structure for the developer --- ## For the impedance toolbox <img src="https://codimd.web.cern.ch/uploads/upload_0a265d1a1224796ec1ab0c6f85b2e0d8.png" width="45%"> <img src="https://codimd.web.cern.ch/uploads/upload_d22697ba36dc333603f9c5cfab0cedf1.png" width="20%"> - Default machine configurations in YAML file to have a simpler interface for the Impedance team - The info is used to compute the beam spectrum (numerically, for adjustable bunch spacing) and rf losses --- ## For the impedance toolbox <img src="https://codimd.web.cern.ch/uploads/upload_0a265d1a1224796ec1ab0c6f85b2e0d8.png" width="45%"> <img src="https://codimd.web.cern.ch/uploads/upload_d22697ba36dc333603f9c5cfab0cedf1.png" width="20%"> - **What is needed:** Mostly to get $\beta$, $\gamma$, $t_\mathrm{rev}$. No program needed, only single data points. ---