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
Apologies if this question seems obvious but I wonder if and why the two functions split_and_pad_trajectories() and unpad_trajectories() are necessary, if rollout_storage already stores the Memory class' hidden states?
My understanding is that because the RNNs process the observation sequentially step after step, you'd want to split and pad the observations at every done so you don't pass in the a newly reset environment observation with the hidden states from last time step. But I wonder if this issue is already avoided since RolloutStorage class stores the previous timestep's hidden states along with the current timestep's observation, i.e.
hidden states
observation
actions
...
$$\text{hiddenStates}_{t-1}$$
$$obs_t$$
$$a_t$$
...
...
...
...
...
The text was updated successfully, but these errors were encountered:
Hi there,
Apologies if this question seems obvious but I wonder if and why the two functions
split_and_pad_trajectories()
andunpad_trajectories()
are necessary, ifrollout_storage
already stores theMemory
class' hidden states?My understanding is that because the RNNs process the observation sequentially step after step, you'd want to split and pad the observations at every
done
so you don't pass in the a newly reset environment observation with the hidden states from last time step. But I wonder if this issue is already avoided sinceRolloutStorage
class stores the previous timestep's hidden states along with the current timestep's observation, i.e.The text was updated successfully, but these errors were encountered: