Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

games stuck at certain steps (location ids) #64

Open
Oaklight opened this issue Jun 2, 2023 · 6 comments
Open

games stuck at certain steps (location ids) #64

Oaklight opened this issue Jun 2, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@Oaklight
Copy link

Oaklight commented Jun 2, 2023

I have been using Jericho for some projects, trinity always gets stuck at these steps when calling env.get_valid_actions()

TRINITY_STUCK_STEPS = set(
    [8, 13, 23, 29, 33, 35, 39, 43, 47, 49, 58, 59, 60, 65, 68, 69]
)

Actually, later I found it's the location id that matters. Here are the ones for trinity and sherlock

TRINITY_STUCK_LOC_ID = (79, 354, 144, 355, 531, 179, 371, 121, 438, 576, 323, 319, 575, 80, 316)
SHERLOCK_STUCK_LOC_ID = (111, 3, 37, 33, 93, 71, 5, 73, 1, 85, 295, 52, 57, 21, 69, 27, 12)
@Oaklight Oaklight changed the title Trinity stuck at certain steps games stuck at certain steps (location ids) Jun 2, 2023
@MarcCote
Copy link
Collaborator

MarcCote commented Jun 2, 2023

Hi @Oaklight , would you mind trying with this WIP branch I have and let me know if that still hangs?

pip install https://github.com/MarcCote/jericho/archive/refs/heads/fix_obj_num.zip

@MarcCote MarcCote self-assigned this Jun 2, 2023
@Oaklight
Copy link
Author

Oaklight commented Jun 4, 2023

Hi @MarcCote, I tried this pip fix, but Trinity is still stuck at location 79, which prevents me from testing further. I didn't test Sherlock.

Meanwhile, I think this behavior might be useful for debugging:
I can't ctrl+c to stop the running process of the Trinity emulator, only able to kill it in my Linux task manager.
some error messages I see repeatedly (they are the same as the ones before applying the pip fix):

KeyboardInterrupt
Traceback (most recent call last):
  File "/home/me/mambaforge/envs/my_env/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
    self.run()
  File "/home/me/mambaforge/envs/my_env/lib/python3.11/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/me/mambaforge/envs/my_env/lib/python3.11/multiprocessing/pool.py", line 114, in worker
    task = get()
           ^^^^^
  File "/home/me/mambaforge/envs/my_env/lib/python3.11/multiprocessing/queues.py", line 364, in get
    with self._rlock:
  File "/home/me/mambaforge/envs/my_env/lib/python3.11/multiprocessing/synchronize.py", line 95, in __enter__
    return self._semlock.__enter__()
           ^^^^^^^^^^^^^^^^^^^^^^^^^

Hope this could be of some help.

@Oaklight
Copy link
Author

Hi @Oaklight , would you mind trying with this WIP branch I have and let me know if that still hangs?

pip install https://github.com/MarcCote/jericho/archive/refs/heads/fix_obj_num.zip

this fix corrected the object tree error in walking the walkthrough in these games for me when using jericho==3.1.2

tryst205
deephome
spirit
curses
advent

@MarcCote
Copy link
Collaborator

That's great. Thank you for reporting this.

@Oaklight
Copy link
Author

Oaklight commented Nov 9, 2023

Meanwhile, we also noticed the fix altered the env.get_walkthrough on many games. Seed was set as default.
Many typos appeared in the observations after taking each step, such as missing first letter, missing space, missing 'the', trailing dots.

@MarcCote
Copy link
Collaborator

MarcCote commented Nov 9, 2023

That is very helpful. Thanks for reporting.

@MarcCote MarcCote added the bug Something isn't working label Nov 9, 2023
@MarcCote MarcCote pinned this issue Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants