Skip to content
Discussion options

You must be logged in to vote

Hi @cosmin-aron! Thanks for sharing your question here. I think I understand the problem you are trying to solve, but I do not really grasp the issue you are facing.

In any case, let me share how events unfold in ALPypeRL (I hope it can help clarify your questions):

  1. requestAction() is called from your simulation side.
  2. The python side receives the request and generates a new action.
  3. The new action is passed to your simulation and consumed by the takeAction(RLAction action) function.

All of the above happens at t=t. Or, in other words, there's no gap in between. This is instantaneous.

In your case, it seems that the problem might come from AnyLogic directly, not ALPypeRL. I don't think yo…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@cosmin-aron
Comment options

Answer selected by cosmin-aron
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants