Tags give the ability to mark specific points in history as being important
-
01.09.03
990fbc3d · ·New PATCH release 01.09.03 Changes since 01.09.02: fix: bunch length definition
-
01.09.02
bc36a345 · ·New PATCH release 01.09.02 Changes since 01.09.01: * fix channel-dependent AOM trigger rounding if truncation of AOM trigger to allowed period happened, we want to be noticed on displayed status
-
01.09.01
ceb23942 · ·New PATCH release 01.09.01 Changes since 01.09.00: * fix: external setpoints check
-
01.09.00
b9ec0855 · ·New MINOR release 01.09.00 Changes since 01.08.00: * improve timing drift feedback give more feedback to operator * fix: write-back pixUpper,pixLower only when time axis was not yet set. This is required for consistent startup parameters. * fix: initial values for StatusAggregator For ApplicationModules waiting on initial values from other modules, we must initialize their StatusOutputs already in prepare, so that StatusAggregator can start up. * some changes for update on FLASH/FL23 goal is background detection and peak detection but skip normalization * for channel1, use linear extrapolation of time axis since constant interpolation will be quite misleading in the plots - even if values are later not used due to cut-off bounds * rework line number inputs * LINES_NUM should not be multiplied by factor 2 * we have DET.SELECTED_LINE_NUMBER which applies to raw image * for each channel, we have a selected bunch line, relative to BUNCHES range * fix: bunchPattern input is signed int * communicate only partial images (EVEN/ODD) parts * update timing drift algo At the time when timing drift feedback is turned on, store the new operation setpoint in terms of wanted offset versus center of time domain * design change: split image on level of modules two instances each of {ImgProc, BunchDetection, BunchTiming} This should improve performance via parallel processing, ease doocs configuration when mapping image parts to different locations, and decouple module interdependencies. We anyway need to have implement different time axes for even/odd part. * changes for recompiled fw fw register names have changed slightly due to changes in fw framework * UserStatistics * separate bunch metrics spectra in SPLIT mode -
01.08.00
be2c76d2 · ·New MINOR release 01.08.00 Changes since 01.07.01: use data_matching=historized in config
-
01.07.01
5139da33 · ·New PATCH release 01.07.01 Changes since 01.07.00: * improve stability in testing have seen problems at startup with invalid data split up extServer device for better error display fix: cycle of bad DataValidity
-
01.07.00
c5f33604 · ·New MINOR release 01.07.00 first release for Ubuntu/noble Changes since 01.06.03: * improvement: timing drift feedback uses tMedian * fix: use base detector freq = 1.1 MHz for AOM freq * use new MatchingMode::historized * minor improvement: get rid of toggling global status
-
01.06.03
cd90010a · ·New PATCH release 01.06.03 Changes since 01.06.02: * improve: bunch detection, reduce false positives by considering line-to-line variation of unmodulated laser signal
-
01.06.02
93725b2b · ·New PATCH release 01.06.02 Changes since 01.06.01: * mp source for image pre-processing module to reduce data loss in DoocsAdapter via config * move noise calc to BunchDetection module
-
01.06.01
61a2226d · ·New PATCH release 01.06.01 Changes since 01.06.00: * bugfixes in BunchTiming module, was crashing
-
01.06.00
7b621803 · ·New MINOR release 01.06.00 Changes since 01.05.02: * use ExtenededSpectrum for standard properties .SAi,.DUD,.ALL * feat: filter by bunch pattern, if requested by operator * fix: detectionSensitivy when using line subsets * remove SPLIT_SAMETIME SPLIT should already imply each line pair belongs to same time * feat: data loss warning via status output. CPU overload in image processing (e.g. too many image lines) can cause data loss. A warning about it may help identify the cause.
-
01.05.02
eab1c0ca · ·New PATCH release 01.05.02 Changes since 01.05.01: * fix: noise level calculation in case of EVEN/ODD line subset, was taking wrong lines * fix: output image line counting first output signal was wrong in case subset=EVEN and BUNCHES.start=odd
-
01.05.01
5efcbabf · ·New PATCH release 01.05.01 Changes since 01.05.00: * fix: write back setpoint DET.lineFreqMult we require that 'restore good timings' returns a consistent state of operation setpoints * fix: rearrange noise level outputs problem was, in control panel for SELECTED_LINE, we did not get meaningful output for deviationOfNoise. Fixed it by introducing new output property. * fix: noise calculation if selected line subset=EVEN/ODD/SPLIT, mean was calculated incorrectly * fix: output images need to be initialzed to zero first since not always completely written * fix: recent bug in time calibration we cannot assume that input data is sorted
-
01.05.00
98e73ec4 · ·New MINOR release 01.05.00 Changes since 01.04.00: * feat: background as moving avg * change SELECTED_LINE meaning it is now before duplication of detector freq * rename config to default name * add prop: beam region selection for MEAN * feat: image splitting into EVEN,ODD this comes with some new properties for signal 2 * feat: set Kalypso line frequency from eod_server for double detector freq * feat: aggregated global status * improve stability of timing drift feedback we must ensure spuriously detected bunches from pure noise signal do not lead to applied timing corrections * improve: moving average calculation track time axis and use linear interpolation, since time axis can change for various reasons * improve: only allow laser delay change if RF locked this is a limitation of the laser_lock_server. We must check state in order not to corrupt consistency of our setpoints * improve calibration procedure: sort out values not in time range * improve calibaration procedure apply fit function to laserDelay=f(bunch center pixel coord) instead of laserDelay=f(measured bunch center time). The previous approach had the problem that a bad calibration that was in effect, could not always be corrected by re-calibration -
01.04.00
3a6d761b · ·New MINOR release 01.04.00 Changes since 01.03.07: * improvement: apply calib should not discard visible scan data like that quality of applied calibration function becomes transparent to operators * fix: debug messages for data loss * feat: timing drift feedback
-
01.03.07
af265f24 · ·New PATCH release 01.03.07 Changes since 01.03.06: * fix: array sizes in BunchTiming * feat: x2timer sync with bunchesStartTimeIndex in order to conveniently select odd bunches
-
-
01.03.05
3323061c · ·New PATCH release 01.03.05 Changes since 01.03.04: * feat in EodScan: user given range cut for time axis fit This is needed because currently server cannot decide whether bunch peaks are from actual bunches or from wake fields
-
-
01.03.03
4377c0e9 · ·New PATCH release 01.03.03 Changes since 01.03.02: x2timer settings: avoid adding up of rounding errors