-
Notifications
You must be signed in to change notification settings - Fork 88
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
update the generation code compatible with ai2thor 2.4.0 (latest) #45
base: master
Are you sure you want to change the base?
Conversation
Thanks @jiasenlu! I'll look into this soon. There are couple of issues with upgrading to 2.4.0:
|
yes, I just fixed some API changes of Thor and it can generate scene for all goals. could you verify that the new code work properly? Thanks! |
@MohitShridhar one quick question, when doing a reply check, what is the success Rate? I do see some error that some object is blocking the way I wonder is this common? Success Rate: 84.50/122.50 = 0.690
|
Ah yes, this navigation failure happens often. The A* navigator use a primitive grid-map representation to plan, so it's not very robust to different sized collision boxes of objects in the Unity scene. |
I checked out this branch and tried building + running the docker, but there's what looks like a torchvision compatibility issue (the docker still installs Python 3.5.2, torch 1.5.1, and torchvision 0.6.1). I can't
I also have not started any x servers in side the docker (i.e. haven't run |
I'll keep this PR open to anyone interested in using 2.4.0 (or higher) for generating new trajectories. Thanks @jiasenlu for looking into this! Feel free to push your latest updates. Unfortunately, we can't merge this into master because the language annotations were collected with 2.1.0. Minor changes to the scene layouts between 2.1.0 and 2.4.0 could invalidate some referring expressions and instructions in the dataset. |
No description provided.