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

Moving Output Objective #442

Merged
merged 4 commits into from
Oct 8, 2024
Merged

Moving Output Objective #442

merged 4 commits into from
Oct 8, 2024

Conversation

jduerholt
Copy link
Contributor

This PR adds the possibility of smart objectives that change during the optimization campaign. So far only the MovingMaximizeSigmoidObjective is implemented (out of an actual need). It changes its turning point based on the best so far achieved value.

@jduerholt jduerholt requested a review from bertiqwerty October 2, 2024 13:16
Copy link
Contributor

@bertiqwerty bertiqwerty left a comment

Choose a reason for hiding this comment

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

Hi Johannes, Thanks. Also this new feature would benefit from documentation/example, I think.

Copy link
Contributor

@bertiqwerty bertiqwerty left a comment

Choose a reason for hiding this comment

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

After discussing with Johannes we decided to first merge this. Johannes will add a more extensive documentation afterwards.

@jduerholt jduerholt merged commit cffd409 into main Oct 8, 2024
9 of 10 checks passed
@jduerholt jduerholt deleted the feature/moving_output_constraint branch October 8, 2024 12:11
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