-
Notifications
You must be signed in to change notification settings - Fork 167
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
Failed to eval finetuned model on aloha-sim-cube
gym environment
#34
Comments
Thanks for giving the model a try! For the model loading: it's surprising that it tries to load a key "diffusion_model" since the |
I'm able to import sim_env, but the example 03_eval_finetuned throws the On changing line 72 in 03_eval_finetuned.py to |
I encountered the same problem, my device did not have enough GPU memory to fine-tune on the aloha environment, and I did not get the results after fine-tuning. So I am not sure if it is caused by not doing inference on the results of fine-tuning. But I checked the dataset_statistics.json file and found that the proprio of all datasets has 8 dimensions, so I think it should also have 8 dimensions after fine-tuning. You can see the config after fine-tuning from this issue #42 (comment), it shows that the action_dim is 14 instead of 8. |
Yes, ALOHA is a bimanual setup so its action space is 14-dimensional. Our pre-training data is all single-arm data with an 8-dimensional action space. |
Hi, thanks for your great work!
I have finetuned the model by using
examples/02_finetune_new_observation_action.py
. And I'm runningexamples/03_eval_finetuned.py
to show the finetuned results.I followed the instructions
octo/examples/03_eval_finetuned.py
Lines 9 to 11 in 8fe7497
and add
sys.path.append("/path/to/act")
. But still cannot makegym.make("aloha-sim-cube-v0")
successful.Another problem is that I cannot successfully load the finetuned model. Here's the backtrace.
It looks like I didn't save the diffusion model in the training process. Did I miss something in the configuration?
Thanks.
The text was updated successfully, but these errors were encountered: