-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add COBYQA optimizer #153
Open
schmoelder
wants to merge
53
commits into
dev
Choose a base branch
from
feature/add_cobyqa
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add COBYQA optimizer #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, there were two interfaces in the `OptimizationProblem` for calling evaluation functions (e.g. objectives): one for evaluating individuals, and one for populations. To simplify the code base, these two methods were now unified. To ensure backward compatibility, a 1D-Array is returned if a single individual is passed to the function.
Co-authored-by: r.jaepel <[email protected]>
Previously, the cadet path set in Cadet(install_path="path") was not inherited into cadet instances created from the run() method.
Fix and extend tests about .calculate_interstitial_rt/velocity
Previously, this was required because CADET-Core was not setting the PATH correctly. Now, this can lead to inconsistent behaviour. Note, this requires CADET>4.4.0
Recently, the option to (not) plot the time axis using minutes was introduced. This commit fixes some methods that were not properly implemented. Moreover, the name of the flag was changed from `use_minutes` to `x_axis_in_minutes` to make clear that only plotting is affected and not other parameter values (e.g. start and end times).
Co-authored-by: daklauss <[email protected]>
This has been implemented, hoping to address issues with COBYLA. Maybe we don't really need this once precision is enabled?
…face SLSQP and COBYLA currently do not support scipy's new callback interface.
schmoelder
force-pushed
the
optimizer_improvements
branch
from
July 23, 2024 14:14
7dd6b54
to
8261d6f
Compare
schmoelder
force-pushed
the
optimizer_improvements
branch
4 times, most recently
from
August 6, 2024 11:45
db2a9ee
to
4062efa
Compare
schmoelder
force-pushed
the
dev
branch
11 times, most recently
from
December 4, 2024 16:47
35e0c67
to
d97cf31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
COBYQA
optimizer which was recently added to SciPy, in v1.14.To do
x0
is infeasible with respect to some inequality constraint even though it is within bounds." (see #155)Open question
This PR also updates the callback function for scipy optimizers. I was hoping that this would include the current best point instead of simply the latest point. This would remove the need to determine the optimal points ourselves using the
ParetoFront
class. However, this is not how it's implemented inCOBYQA
(see here).Note, this interface is not supported by
COBYLA
andSLSQP
, so these optimizers would have to be removed from CADET-Process when using the newer interface. SinceCOBYQA
can replaceCOBYLA
, I don't mind it going butSLSQP
might be handy to keep around. So should we revert these changes (for now)?Edit: Instead of removing
COBYLA
andSLSQP
, provide both interfaces and switch depending on the selected method.