Closed klieret closed 6 months ago
I think this is a deprecated feature related to something we explored that didn't end up making it into the final model. @john-b-yang will know for sure.
Being able to do replays is quite nice for testing purposes (like testing the "open PR" mechanism etc.). If it's not much used right now, I'll just merge the fix for now and we can remove the whole thing later if we choose so.
ah ok if you found a use for this we should keep it! thanks
I just cleaned up this file a bit in db344162b1d243eff87fd5fb291313839ba99124 (mainly just removed process_synthetic_trajs
function, --action_trajs_path
argument).
This a helpful file. The main use case is if a user is interested in creating a demonstration for a new configuration from an existing set of actions (reflected by the --traj_path
argument). Instead of having to create it manually with python run.py --model human ...
, one can just run
python run_replay.py \
--traj_path trajectories/carlosejimenez/<experiment>/pallets_flask-123.traj \
--config_file config/<new config file name>.yaml \
--data_path path/to/file/with/pallets_flask-123-task-instance.jsonl # Optional, automatically inferred from experiment folder if available \
--suffix run1 # Optional \