Closed aphedges closed 1 year ago
In retrospect, it seems like referencing the tasks by either the ID in the paper (e.g. "3-1") or their detailed name (e.g. "create-a-circuit") is the way to go, since it makes sure there's no ambiguity. The 0-29 numbering that's auto-sorted seemed great in development, but seems less great in retrospect. :)
@aphedges thank you again. I'll make a new patch release (1.1.3) today.
Building off the work in #44, I've made some improvements to the handling of task names while hopefully maintaining backwards compatibility.
The new file
tasks.json
was generated using the files in json_creation.zip:task_names.json
: A file created for internal use from data in the paper and repositoryconvert.py
: A script to combine our JSON file and yourdict
s into a new file for inclusion in the libraryI didn't actually test my changes by running ScienceWorld, but the tests make me pretty confident it would work.