Skip to content
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

Default value for eval_horizon #337

Open
TimotheeMathieu opened this issue Jul 12, 2023 · 7 comments
Open

Default value for eval_horizon #337

TimotheeMathieu opened this issue Jul 12, 2023 · 7 comments

Comments

@TimotheeMathieu
Copy link
Collaborator

Should the default for eval_horizon be 500 ?

@omardrwch
Copy link
Member

I'd keep it as large as possible (as now) and put a time limit in the environment, if necessary. To avoid hiding these choices from the user.

@KohlerHECTOR
Copy link
Collaborator

Yes it should be 500 but could be change, it does not really matter.

@omardrwch
Copy link
Member

omardrwch commented Jul 14, 2023

Yes it should be 500 but could be change, it does not really matter.

Why should this be 500? @KohlerHECTOR

@omardrwch omardrwch reopened this Jul 14, 2023
@TimotheeMathieu
Copy link
Collaborator Author

This should be 500 because 500 is the default for all control gym environment and is used in most benchmarks of control environments. This may be a deep rl thing. I think that there is no default in tabular rl so I think it is best to just go with the default that exists in deep rl.

@omardrwch
Copy link
Member

If the gym environment has already a time limit (at 500), any eval_horizon > 500 will do the job. So I'd keep as large as possible by default. Some atari environments have pretty huge horizons (~30k).

@KohlerHECTOR
Copy link
Collaborator

@omardrwch Sorry for the authoritarian closing. I think indeed 500 is some kind of industry standard let us say. But in any case, this could be changed by the user when they code their experiments. Plus evaluation is pretty costly so on the contrary I would keep it as low as possible :)
I guess in a dream world, we would have some config files with suggested values for n_steps n_evals eval_horizonfor different envs :)

@omardrwch
Copy link
Member

No worries! Ok for 500, but then let's put warning if we've reached 500 and the episode is not terminated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants