- Jul 04, 2019
-
-
Martin Killenberg authored
-
- Jun 25, 2019
-
-
Martin Christoph Hierholzer authored
rename VersionNumberUpdatingRegisterDecorator into MetaDataPropagatingRegisterDecorator, as it does more than just updating the VersionNumber now
-
Martin Christoph Hierholzer authored
-
- Jun 05, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- May 23, 2019
-
-
Jens Georg authored
-
- May 22, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- May 13, 2019
-
-
Martin Christoph Hierholzer authored
-
- May 08, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- May 07, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- May 06, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Nadeem Shehzad authored
changed: deviceModule run is called before readLatest for comusming direction variables. removed: impl->write() for NodeType::Device.
-
Nadeem Shehzad authored
changed: device is not intialized in constructor anymore.
-
- May 02, 2019
-
-
Nadeem Shehzad authored
-
Nadeem Shehzad authored
-
Nadeem Shehzad authored
Test still does not work. -Unable to get the exception status for the device throwing exception. -Second device only works it has it's own trigger.
-
- May 01, 2019
-
-
Zenker, Dr. Klaus (FWKE) - 126506 authored
-
- Apr 29, 2019
-
-
Martin Christoph Hierholzer authored
- removed debug output - made implementation for not-fixed feeders (i.e. ApplicationModule feeders) of the trigger network identical to the implementation for fixed feeders
-
Martin Christoph Hierholzer authored
According to ChimeraTK/DeviceAccess#61 Devices will no longer close on their own (e.g. when throwing an exception). The exception handling now takes into account that the device always stays open
-
Martin Christoph Hierholzer authored
TriggerFanOut must catch exceptions when reading from the TransferGroup, since this cannot be handled by the decorator
-
Martin Christoph Hierholzer authored
-
-
Creation of fanOuts is based on externalTriggerImpl (=trigger consumer), not externalTriggerNode (=trigger feeder). - Fixes connection network but not exception handling. - Lots of debug output left in the code for further investigation.
-
-
- Apr 26, 2019
-
-
Martin Christoph Hierholzer authored
fixed a potential invalid read/write error, access to object and its potential destruction was done in wrong order
-
- Apr 12, 2019
-
-
Jens Georg authored
- Have a ZMQ push-type variable from a DOOCS-backed device that is NOT used as a trigger (otherwise the bug does not happen) - Connect that to an ScalarPushInput in an ApplicationModule - call readAnyGroup() from the ApplicationModule's main method => ReadAnyGroup.finalise() will cause an infinite recursion between ExceptionHandlingDecorator::doReadTransferAsync and TransferElement::readAsync because of wrong dispatching to the decorated type
-
- Apr 02, 2019
-
-
Martin Christoph Hierholzer authored
-
- Mar 20, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Mar 19, 2019
-
-
Martin Christoph Hierholzer authored
- add test for full exception handling
-
- Mar 18, 2019
-
-
Martin Christoph Hierholzer authored
DeviceModule and ControlSystemModule now do not take the optional prefix argument in their constructors any more. Use the [] operator instead to get the submodule. - Add ExceptionHandlingDecorator and decorate all device variables with it.
-
- Mar 11, 2019
-
-
Martin Christoph Hierholzer authored
move ApplicationModule::appConfig() to ModuleImpl::appConfig() so it can also be used from ModuleGroup
-
- Mar 08, 2019
-
-
Martin Christoph Hierholzer authored
-
- Feb 28, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-