You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks a lot for providing this wonderful benchmark and environment.
Our team are developing based on the BrowserGym environment (trying to wrap over the BrowserEnv class). I wonder what the teardown function actually do for each task type. Is there any problem if we do not call this function after a series actions (w/ or w/o invoking the validate function)? It seems it will influence the history on cloud ServiceNow DB records.
If you are developing an agent, the task.teardown() function is not meant to be called directly by you. It will be called by the BrowserEnv environment upon termination of an episode (env.reset() and env.close()).
if you are developing a new task, implementing this method is optional. It gives you the possibility to clean things up once the agent is done interacting with the environment (e.g., deleting temporary data). it you not be relied upon too much though, as if your program terminates in the middle of an episode (agent or environment failure) there is no guarantee this method will be called at all.
Activity
gasse commentedon May 14, 2024
Hi @rhythmcao , thank you for your interest!
If you are developing an agent, the
task.teardown()function is not meant to be called directly by you. It will be called by theBrowserEnvenvironment upon termination of an episode (env.reset()andenv.close()).if you are developing a new task, implementing this method is optional. It gives you the possibility to clean things up once the agent is done interacting with the environment (e.g., deleting temporary data). it you not be relied upon too much though, as if your program terminates in the middle of an episode (agent or environment failure) there is no guarantee this method will be called at all.
Hope this helps