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

ESS optimizers: suppress divide-by-zero warnings; report n_eval #1380

Merged
merged 1 commit into from
May 2, 2024

Conversation

dweindl
Copy link
Member

@dweindl dweindl commented Apr 30, 2024

For ESSOptimizer and SacessOptimizer:

  • supporess divide-by-zero warnings
  • report number of function evaluations

For ESSOptimizer and SacessOptimizer:
* supporess divide-by-zero warnings
* report number of function evaluations
Copy link
Collaborator

@PaulJonasJost PaulJonasJost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks :)

abs(abs_change / self._best_known_fx.value)
if self._best_known_fx.value != 0
else np.nan
)
self._logger.debug(
f"Rejected solution from worker {sender_idx} "
f"abs change: {abs_change} "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is relative change formatted to at most four digits but absolute change not?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤷‍♂️
Couldn't decide on what's reasonable yet.

@dweindl dweindl merged commit e197a8b into ICB-DCM:develop May 2, 2024
15 of 18 checks passed
@dweindl dweindl deleted the ess_log_neval branch May 2, 2024 17:00
This was referenced May 27, 2024
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

Successfully merging this pull request may close these issues.

2 participants