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

Consistency of maxevals property with evals property #2092

Closed
nikohansen opened this issue Mar 29, 2022 · 2 comments
Closed

Consistency of maxevals property with evals property #2092

nikohansen opened this issue Mar 29, 2022 · 2 comments
Labels

Comments

@nikohansen
Copy link
Contributor

Should the property DataSet.maxevals rather return DataSet.maxfgevals when testbedsettings.current_testbed.has_constraints, to be consistent with the evals property? This would avoid code like this

if testbedsettings.current_testbed.has_constraints:
    # maxevals is inconsistent in that case
    maxevals_column = entry.maxfgevals
else:
    maxevals_column = entry.maxevals

Could there be undesired side effects?

@nikohansen
Copy link
Contributor Author

nikohansen commented Apr 19, 2022

Probably in the current ERT value computation with the constrained testbed, the unsuccessful runs are for this reason by a factor of 2 off.

@nikohansen
Copy link
Contributor Author

To be continued with #2106.

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

No branches or pull requests

1 participant