-
Notifications
You must be signed in to change notification settings - Fork 321
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
ScalarizedOutcomeConstraint support (e.g. sum outcome constraint) #472
Comments
Hi, @reiter-ja! This functionality is currently not supported, unfortunately, but not because there is a methodological blocker –– it's just something we have not yet had requests for and therefore have not dedicated the engineering effort to. We'll look into adding support for this, and I will let you know once we have a plan (or a decision that we are not supporting this in the short term). |
Update on this: while we are interested in supporting this functionality, we probably will not get to it in the short-term, so marking this item as 'wishlist' for now. |
Support for Ax/ax/utils/testing/core_stubs.py Line 736 in 464ac62
cc @qingfeng10 who added support for this functionality |
This is now done and included with latest stable release, 0.2.0. |
Hello Ax team,
Is there a way to use SumConstraint() as an OutcomeConstraint() with a set of different metrics?
Background:
I have a set of metrics, each of them depends on three input parameters:
Metric1 = f(x1,x2,x3)
Metric2 = f(x4,x5,x6)
Metric3 = f(x7,x8,x9)
Now I want to set an outcome constraint like:
Limit <= Sum(Metric1, Metric2, Metric3)
Right now I use python to calculate the sum of the three different metrics and define a fourth metric like:
Metric4 = np.sum( Metric1, Metric2, Metric3)
and then I define one single OutcomeConstraint based on Metric4.
However, I think now it is much harder for Ax to learn the behavior of Metric4.
Many thanks in advance for the answer :-)
Best regards,
Jakob
The text was updated successfully, but these errors were encountered: