This PR adds better handling for invalid values of trigger_interval_ticks, in particular zero. In the moo schema, the trigger_interval_ticks value in constrained to be at least 1. Unfortunately, moo currently doesn't do numeric constraints validation when generating from python objects, so this has no effect (yet).
In the TriggerDecisionEmulator class itself, the value of trigger_interval_ticks is checked in do_start and do_resume, with an exception thrown if it's zero
This PR adds better handling for invalid values of
trigger_interval_ticks, in particular zero. In the moo schema, thetrigger_interval_ticksvalue in constrained to be at least 1. Unfortunately, moo currently doesn't do numeric constraints validation when generating from python objects, so this has no effect (yet).In the
TriggerDecisionEmulatorclass itself, the value oftrigger_interval_ticksis checked indo_startanddo_resume, with an exception thrown if it's zero