133 lines
2.6 KiB
Plaintext
133 lines
2.6 KiB
Plaintext
# Change Log
|
|
|
|
## 2025.101
|
|
|
|
### Fixed
|
|
|
|
- Improved performance significantly when requesting many channels from
|
|
an upstream caps server.
|
|
|
|
## 2025.069
|
|
|
|
### Changed
|
|
|
|
- Ported code to latest SeisComP API 17 and fix deprecation
|
|
warnings.
|
|
|
|
## 2024.262
|
|
|
|
### Fixed
|
|
|
|
- MiniSEED encoding allows half a sample timing tolerance
|
|
to detect contiguous records.
|
|
|
|
## 2023.234
|
|
|
|
### Added
|
|
|
|
- Command-line help and more module documentation.
|
|
|
|
## 2023.257
|
|
|
|
### Added
|
|
|
|
- New configuration option `maxRealTimeGap` and `marginRealTimeGap`.
|
|
They allow to configure a dedicated backfilling stream and to
|
|
prefer real-time data. The consequence is the reception of
|
|
out of order records at clients.
|
|
|
|
## 2022-02-28
|
|
|
|
### Added
|
|
|
|
- New config option `timeWindowUpdateInterval`. This option
|
|
sets the interval in seconds at which the relative request
|
|
time window defined by option `days` and/or `daysBefore` is
|
|
updated. Use a value less or equal zero to disable the update.
|
|
This feature is supported in archive mode only.
|
|
A typical use case is when data has to be transmitted
|
|
continuously with a time delay.
|
|
|
|
```bash
|
|
timeWindowUpdateInterval=86400
|
|
```
|
|
|
|
## 2022-02-25
|
|
|
|
### Fixed
|
|
|
|
- Wrong time window subscription after reconnect
|
|
|
|
## 2020-12-22
|
|
|
|
### Added
|
|
|
|
- Configuration description for daysBefore in e.g. scconfig
|
|
|
|
## 2020-12-17
|
|
|
|
### Added
|
|
|
|
- New config option `daysBefore` which can be used to set the end time
|
|
of the data acquisition time window n days before the current time, e.g.,
|
|
|
|
``` bash
|
|
daysBefore=10
|
|
```
|
|
|
|
## 2020-02-17
|
|
|
|
### Changed
|
|
|
|
- Increase default timeout for acknowledgement messages from 5s to 60s
|
|
- Use microsecond precision in data requests
|
|
|
|
## 2020-02-12
|
|
|
|
### Added
|
|
|
|
- Backfilling buffer which is a tool to mitigate out-of-order data. Whenever a
|
|
gap is detected, records will be held in a buffer and not sent out. Records
|
|
are flushed from front to back if the buffer size is exceeded.
|
|
|
|
## 2020-02-10
|
|
|
|
### Changed
|
|
|
|
- Subscribe to streams even if the requested end time is before the last
|
|
received timestamp. This is necessary to do not request data again in
|
|
case of wildcard requests.
|
|
|
|
## 2018-08-05
|
|
|
|
### Fixed
|
|
|
|
- segfault in journal file parser
|
|
- corrupt journal files
|
|
|
|
## 2018-03-19
|
|
|
|
### Added
|
|
|
|
- SSL support for outgoing connections
|
|
|
|
## 2018-03-14
|
|
|
|
### Fixed
|
|
|
|
- The journal file will be stored by default at @ROOTDIR@/var/run/[name]/journal
|
|
where name is the name of the application. In standard cases it is ```caps2caps```
|
|
but not with aliases in use.
|
|
|
|
## 2017-03-21
|
|
|
|
### Fixed
|
|
|
|
- stream recovery in case of wild card request
|
|
|
|
## 2017-02-14
|
|
|
|
### Added
|
|
|
|
- out-of-order support
|