dodox/Columbus
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix: Fatal Bug, max_steps always triggering

Browse Source
This commit is contained in:
Dominik Moritz Roth 2022-10-14 15:23:40 +02:00
parent 811b2bb1e3
commit 83eb759b9c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
columbus/env.py
View File

@ -219,7 +219,7 @@ class ColumbusEnv(gym.Env):
reward += self._get_aux_reward() reward += self._get_aux_reward()
self._steps += 1 self._steps += 1
done = self._term_next or (self.die_on_zero and self.score <= 0) or (self.return_on_score != - done = self._term_next or (self.die_on_zero and self.score <= 0) or (self.return_on_score != -
1 and self.score > self.return_on_score) or self._steps >= self.max_steps 1 and self.score > self.return_on_score) or self._steps == self.max_steps
# make sure we register the current reward # make sure we register the current reward
self._term_next = self.terminate_on_reward and gotRew self._term_next = self.terminate_on_reward and gotRew
info = {'score': self.score, 'reward': reward} info = {'score': self.score, 'reward': reward}