too early or late step call

[NDR008]

What happens when a call to step() of rtgym is called too early? Say after 5ms when a timestep of 50ms was set?

[yannbouteiller]

The call blocks untill an observation is captured. This is how rtgym synchronizes timesteps, and it expects you to call step before the end of the timestep (within some allowed elasticity) otherwise it times out and throws a warning.

[NDR008]

May need to come back to this question. After I process it better. :)

…

On Wed, 18 Oct 2023, 14:28 Yann Bouteiller, ***@***.***> wrote: The call blocks untill an observation is captured. This is how rtgym synchronizes timesteps, and it expects you to call step before the end of the timestep (within some allowed elasticity) otherwise it times out and throws a warning. — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIKWRWXB2OKQEJUW5ZXOHJLX77DQLAVCNFSM6AAAAAA6ELRLJ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGMJUG4ZDO> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[yannbouteiller]

Well, the flow is approximately this:

• You send an action to rtgym and retrieve an observation from step(). At this point rtgym starts applying this action.

• Meanwhile, you compute a new action from the retrieved observation, and call step() again to send this action to rtgym when you are done (before the current time-step ends).

• rtgym waits untill the end of the current time-step to return with a new observation, and starts applying your computed action.