- ControlSystemModule
- VirtualModule
- findTag
- excludeTag

and some related functions.

Jens Georg authored 2 years ago and Martin Christoph Hierholzer committed 2 years ago

 - ApplicationModule can only be owned by ModuleGroup

Modernise interface of status monitors and add tests of initial value propagation and data validity propagation (#8279). Improve code formating/readability.

Using the DESY identifier here was done by mistake when introducing the SPDX headers.

Co-authored-by: Martin Hierholzer <martin.hierholzer@desy.de>

* Use templated version to add a trigger.

A trigger is needed for Poll type inputs. Still it can not be used for
Devices. Here one has to call addSource manually.

* No need to use a trigger. Fix connections by moving all to history.

Trigger is only needed for DeviceModules. So in case of device addSource
still needs to be used, because no tags are present for devices.

* Add option to specify the directory where history will appear in CS.

* Remove CS tag not needed any more.

* Update documentation.

* Update documentation of logging module.

* Remove CS tag not needed any more.

* Remove parameter not needed. AddSource for ConnectingDeviceModule. Docu.

* Create test case for testing multiple modules having the same.

* Use message IDs to support modules with similar names.

ToDo: Remove variable connections to CS like with MicroDAQ.

* Use automatic connection via CS. Rebuild hierarchy in Logging module.

* Put logging variables into a separate hierarchy level.

* Let user write to alias via CS. Keep last message in the PV.

Before the message was always cleared after writing it. Now a new log
level is used to indicate the situation that write was called on the
message PV without calling sendMessage - it happens if the owning module
calls writeAll(). Now the last message of each sender is availble in the
CS.

* Add test with modified hierarchy.

* Clang formaat applied.

* Hide internal PVs. Use different internal tag to work with regex.

Introduce StatusWithMessage and StatusWithMessageReader which handle this.
It is used in DeviceModule error reporting.
This is a preparation in order that we can report errors consistently to DOOCS, in DoocsAdapter

make StatusAggregator use StatusWithMessage

it should output always status code + string
on the input side, connects to either status or status + string
corresponding string input is found automatically
NOTE: DeviceModule API change, the status output variables are
renamed from (status, message) to (status, status_message)!

update testing of DeviceModule outputs

because of API change of DeviceModule  (renamed message ->
status_message)

fix crash and improve message and test

- fix crash due to incorrect handling of cast to Derived
- improve message output
- make existing tests pass
- add test for status message of StatusAggregator

move StatusWithMessageReaderBase and Status def to ControlSystemAdapter

since it is required from ApplicationCore as well as from the adapters

Co-authored-by: d-rothe <39566710+d-rothe@users.noreply.github.com>

Without them, the references become invalid in move operations which leads to subsequent segfaults.

* optimization for StatusAggregator
make getPriority faster by making prio map static and reduce evaluation frequency

* get rid of compiler warning

* comment for statusPrio

Co-authored-by: Dietrich Rothe <dietrich.rothe@desy.de>

ScriptedInitialisationHandler: catch boost exceptions and throw ChimeraTK logic_error with improved what() message