Several issues regarding termination and truncation of signal processing #427
Unanswered
Wangzai-hub
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When _time_limit_bootstrap is set to True, the processing logic is similar to:
The code adds the current state value. Should it instead add the state value of the next moment?
If _time_limit_bootstrap is set to True, when terminated = False and truncated = True, in version 2.0, does GAE's calculation add next_values again?
Should we pass ‘dones=self.memory.get_tensor_by_name("terminated") | self.memory.get_tensor_by_name("truncated")‘ here as we did in version 1.4.3?
Meanwhile, in some environment implementations, when the environment ends (terminated or truncated = True), such as in isaaclab (see the code at the bottom), the reset function is called, and then the state after reset is returned, not the state after the action is executed. Can passing in ’done = self.memory.get_tensor_by_name("terminated") | self.memory.get_tensor_by_name("truncated")‘ avoid some logical issues?
Beta Was this translation helpful? Give feedback.
All reactions