Closed Cpache1 closed 4 years ago
Using the legacy code might require you to use a legacy overcooked-ai
repo – generally I would recommend to use the new demo code, as for most purposes it should work fine. The old code is not fully supported or documented (as you have noticed yourself) – but if you do want to use that, I would recommend using the latest commit of overcooked-demo
before the repo restructuring, and a paired commit from overcooked-ai
(I just paired by timestamp of the commits). This might be easier to do than working on legacy code from the current codebase.
I see. What I was trying to do is to run the demo on a website with pre-built agents - the ones you made for your paper, discussed in this blog and with which you can play here or see each other play. Did you use legacy code to set that demo up or latest? Also, is it possible to access those pre-trained bots from your previous study? (I guess that might not be in this repo...if not I am happy to post on the specific repository if you point me to it! :) )
The demo here was made using the legacy code only – so those are in fact the pre-trained bots from the initial study published at NeurIPS! We will be clarifying this in a future update.
So, I have been attempting to make this repository work with the main overcooked_ai one and I have run into some issues. For reference, I was attempting to do the Overcooked-Demo-Legacy installation as I need and prefer the .js backend.
Given the previous errors ("no such file"), I figure it had something to do with a missing "cd overcooked-demo-legacy" rather than "cd overcooked-demo" only - so you should add this to your README file. Because once you go into that folder, then you can use 'npm install'. It then gives me this:
How should I proceed?