Create a better notation for button press inputs, or other weird encoding edge cases. #22
Labels
API Usability
Issues related to making the system easier to use on a software level
Projects
@DannyWeitekamp and I ran into an issue with done button presses in CTAT, which canonically send a -1 as the input to their actions. In agents with some kind of math knowledge this triggers a how search over why the input is -1, which can take a long time to learn something arbitrary and incorrect. Further, when it comes time to request a done button action the apprentice might spit out some arbitrary input value based on whatever nonsense it learned in training that won't be accepted by default. Currently we are handling this by altering the actions that come out of the apprentice before we pass them on to CTAT but it would be great if we didn't have to do that.
Here are some ideas for fixing this that I've thought of:
The text was updated successfully, but these errors were encountered: