visualdynamics.gui.shock_panel¶
shock_panel
¶
The shocks found in a time history, as a table beside it.
One row per event: when its window opens and how long it runs. Both are editable, because detection is a good guess and not an oracle — and the same two numbers are what dragging a region on the plot changes, so the table and the trace are two views of one list.
The panel says where the events are, reports when that changes, and its Compute SRS button turns the history into spectra with whatever is set at that moment — the project verb a script calls. That is exactly how the averaging panel stands to a PSD.
Classes:
| Name | Description |
|---|---|
ShockPanel |
The events, and what can be done to them. |
Classes¶
ShockPanel
¶
Bases: QWidget
The events, and what can be done to them.
changed carries the whole list rather than which row moved: the
list is short, the receiver rewrites the overlay from it either way,
and a diff nobody uses is a thing that can be wrong.
Methods:
| Name | Description |
|---|---|
set_shocks |
Show these, without reporting them back as an edit. |
srs_settings |
The analysis choices as |
show_band |
State the band the current windows support. |
Source code in src/visualdynamics/gui/shock_panel.py
67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 | |
Methods:¶
set_shocks
¶
set_shocks(
shocks: Sequence[Shock], locked: bool = False
) -> None
Show these, without reporting them back as an edit.
Source code in src/visualdynamics/gui/shock_panel.py
srs_settings
¶
The analysis choices as compute_srs keyword arguments.