Re: Unexpected duplicate activation with ODLY > 0

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

Hi Ivo,

I guess what you're seeing is - in the calcout record delay: records that process asynchronously re-process once if they are triggered during their active phase. The calcout processes once for the first trigger, then another time when the ODLY is over and it detects that it had been triggered. That second processing starts another ODLY and writes to the target 1 second later.

Apart from that, your database looks pretty over-complicated.

If you can describe what you want to achieve, I'm sure we can point you to a more efficient implementation.

Cheers,
~Ralph