- Apr 30, 2021
-
-
Martin Christoph Hierholzer authored
-
- Apr 28, 2021
-
-
Martin Christoph Hierholzer authored
-
- Apr 26, 2021
-
-
Martin Christoph Hierholzer authored
-
- Mar 23, 2021
-
-
Martin Christoph Hierholzer authored
Co-authored-by:
Jens Georg <jens.georg@desy.de>
-
- Aug 27, 2020
-
-
Martin Christoph Hierholzer authored
-
- Aug 26, 2020
-
-
Martin Christoph Hierholzer authored
Prints a clear message if a circular dependency of initial values exists.
-
- Jul 27, 2020
-
-
Martin Killenberg authored
-
- Jul 09, 2020
-
-
Christoph Kampmeyer authored
-
- Jul 08, 2020
-
-
Christoph Kampmeyer authored
-
- Jul 02, 2020
-
-
Martin Killenberg authored
-
Martin Killenberg authored
-
Christoph Kampmeyer authored
Rearranged processing of fanouts and their consuming nodes. A list of consuming nodes and implementations is passed to the fanout constructors, so the nodes don't have to added later. This resolves conflicts in the order in which accessors are decorated and added to the fanouts. FanOut constructors could still use refactoring.
-
Martin Killenberg authored
- removed ExceptionHandlingDecorator::setOwnerValidity()
-
- Jul 01, 2020
-
-
Christoph Kampmeyer authored
Ongoing refactoring. Consuming fanout works again.
-
Christoph Kampmeyer authored
-
- Jun 30, 2020
-
-
Christoph Kampmeyer authored
-
- Apr 14, 2020
-
-
Martin Christoph Hierholzer authored
allows to control whether to wait for device recoveries in stepApplication
-
- Mar 11, 2020
-
-
Martin Killenberg authored
- All accessors come up in exception state. - Read-accessors increase counter in init phase Assertion is gone, but tests still failing
-
- Feb 27, 2020
-
-
Christoph Kampmeyer authored
- EntityOwner has individual counters for both events - Adapted all instances of increment/decrementDataFaultCounter - Not changed getDataValidity() implementation yet - Tests failing
-
- Feb 04, 2020
-
-
Martin Christoph Hierholzer authored
-
- Jan 31, 2020
-
-
Jens Georg authored
-
- Jan 29, 2020
-
-
Martin Killenberg authored
- Exception handling decorator does not allow to leave testable mode before devices are up - Test facility makes sure that testable mode counter is zero at the end of startApplication()
-
- Jan 22, 2020
-
-
Martin Christoph Hierholzer authored
-
- Jan 21, 2020
-
-
Martin Christoph Hierholzer authored
-
Tomasz Kozak authored
change declaration of 'decrementDataFaultCounter' in 'EntityOwner' to take a bool parameter and adjust rest of the code to it implement 'decrementDataFaultCounter' in 'ApplicationModule' according to ticket #95 -> rewrite all outputs when 'faultCounter' goes from 1 to 0
-
Tomasz Kozak authored
-
- Aug 22, 2019
-
-
Jens Georg authored
size_t has different types on 32 vs 64 bit systems. UL is correct for 64. Just use the ::size_type define to help it figure it out properly
-
- Jun 05, 2019
-
-
Martin Christoph Hierholzer authored
-
- Apr 29, 2019
-
-
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.
-
-
- Mar 20, 2019
-
-
Martin Christoph Hierholzer authored
-
- Mar 19, 2019
-
-
Martin Christoph Hierholzer authored
- add test for full exception handling
-
- Mar 18, 2019
-
-
Martin Christoph Hierholzer authored
-
- Feb 22, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Feb 21, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Feb 13, 2019
-
-
Nadeem Shehzad authored
-
Nadeem Shehzad authored
-
- Feb 04, 2019
-
-
Martin Christoph Hierholzer authored
- treat the two directions of bidirectional variables properly in testable mode (i.e. as individual variables with each one counter) - fix a data race in testable mode in case a bidirectional variable rejected a value (was not holding a required lock)
-