-
Notifications
You must be signed in to change notification settings - Fork 9
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
Remove default non-negativity constraint on least core subsidy #304
Remove default non-negativity constraint on least core subsidy #304
Conversation
When set to True, it constraints the subsidy to be >= 0
…ot using non-negative subsidy constraint
…me way in all functions
Otherwise this would implicitly add the constraint e >= 0
…SCS and default max iters to 10000
(without looking at the PR) Note that the constraint for the empty set only implies e > 0 if u(S)=0 |
And, since you update the docs, would it be possible to keep the notation consistent with the rest of the docs? i.e. identify points |
@mdbenito I actually used the same notation as in the rest of the data valuation documentation. Do you mean only in the docstring? If not, then I would suggest we leave that as a separate issue and discuss it tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just had a couple of questions. Otherwise this looks good. We should repeat the experiments, btw...
Description
This PR closes #294
Changes
non_negative_subsidy
flag to least core methods with a default value of False.non_negative_subsidy=True
)non_negative_subsidy=True
)options
tosolver_options
.solver_options
as dictionary instead of as kwargs.Checklist
"nbsphinx":"hidden"