Overtime info in REXYGEN Diagnostics

[stepan.ozana]

Hi, I'd use some explanation on diagnostics related to overtime. Are Aaverage time, Overtime and Max overtime related to basic tick or to the period of the task? I am asking that question because it's not clear to me. Let's suppose I have two tasks, Qtask ("task_speed_loop", tick=2ms) and Level0 ("task" , 5*2ms=10ms). Looking at diagnostics I get overtime. It's caused by customized Python block containing complex operations. This Python block needs appx 5ms to perform all operations. However, the task is launched every 10 ms so it should be computed in time. It seems like the overtime info is related to basic tick 2 ms. Is this correct or am I wrong? Thanks a lot, Stepan.

[Jan Reitinger]

@stepan-ozana Hello Stepan, the issue lies in the setting of the task values for Level0. By using ntick, multiple time "slots" (ticks) are created in which individual tasks can be performed. The start and stop parameters specify which slots the tasks will run in. With the setting ntick=5, basetick=2ms, this creates 5 ticks of 2ms each for Level0. If you want a task to run across all ticks, you set start=0, stop=5. For the setting start=0, stop=1, the task will run only for one assigned tick, i.e., 2ms. In newer versions of REXYGEN, this can be automatically adjusted by setting start=-1 and stop=-1.

Cheers,
Jan

[stepan.ozana]

@Jan-Reitinger Thank you so much for efficient help. Now it works exactly as I wish.