| Jira | |||||||
|---|---|---|---|---|---|---|---|
|
...
|
Objectives
This module introduces the RTBSA GUI. After completing this module, an operator should be able to:
...
Say that we have a train of pulses with pulse IDs 1 through 4, and say that we have a BPM (beam position monitor) somewhere watching them go by:
...
Where the first row is the pulse ID and the second row is the x position that the BPM saw for that pulse. While the PV is selected, the data buffer keeps getting written to modulo the pulse ID buffer size so that when it sees pulse 5, it would become:
| 5 | 2 | 3 | 4 |
| 0.00 | -0.02 | 0.02 | 0.04 |
|---|
This is pretty much the backbone of the whole program.
A vs. Time
The simplest use case, where we have one PV with one associated data buffer. The default (and maximum) buffer size is 2800, but that can be reduced if desired. Whatever the buffer size n, we display the n most recent points as long as a kind of rolling EKG:
This is useful for seeing erraticisms in a signal (maybe you suspect a klystron phase is wandering), or to see how it's trending (maybe you're messing with a quad and you want to see if that's increasing/decreasing/doing nothing to the pulse intensity).
FFT
TODO ask Ahmed
B vs. A
The crown jewel of RTBSA. If there are two PV selected at once, there are two data buffers getting filled simultaneously