You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An evaluation environment (eval_env) with num_envs > 1, which I use to periodically evaluate the policy.
However, from the second evaluation onwards, the first frame in the recorded video is always the last frame from the previous episode. This happens even though I explicitly call eval_env.reset() before starting the evaluation.
While I consistently observe this issue in my training script, I cannot reproduce it with the following minimal script. Besides, if I set num_envs=1 in my training script (but still run it on GPU), the issue does not occur.
Do you have any insights into what might be causing this issue, especially given that it only occurs with num_envs > 1?
I see. You mention this minimal script can't reproduce the issue? I'm not sure how I can help debug here.
My only guess is that maybe you are using the vector env wrapper which converts the maniskill env into the gymnasium vector env API. That wrapper by default has auto resets, which calls env.reset. I am guessing it does not call your video reset function perhaps in the way you think it does.
In my training script, I have two environments:
eval_env
) withnum_envs > 1
, which I use to periodically evaluate the policy.However, from the second evaluation onwards, the first frame in the recorded video is always the last frame from the previous episode. This happens even though I explicitly call
eval_env.reset()
before starting the evaluation.While I consistently observe this issue in my training script, I cannot reproduce it with the following minimal script. Besides, if I set
num_envs=1
in my training script (but still run it on GPU), the issue does not occur.Do you have any insights into what might be causing this issue, especially given that it only occurs with
num_envs > 1
?The text was updated successfully, but these errors were encountered: