Exercise 1:
The empty set is the only one. For any nonempty set X, you could pick as a counterexample:
Exercise 2:
The agent will choose an option which scores better than the threshold .
It’s a generalization of satisficers, these latter are thresholders such as is nonempty.
Exercise 3:
Exercise 4:
I have discovered a truly marvelous-but-infinite solution of this, which this finite comment is too narrow to contain.
Exercise 5:
The generalisable optimisers are the following:
i.e. argmin will choose the minimal points.
i.e. satisfice will choose an option which dominates some fixed anchor point . Note that since R is only equipped with a preorder, it means it might be a more selective optimiser (if not total, it’s harder to get an option better then the anchor). More interestingly, if there are indifferent options with the anchor (some x / and ), it could choose it rather than the anchor even if there is no gain to do so. This degree of freedom could be eventually not desirable.
Exercise 6:
Interesting problem.
First of all, is there a way to generalize the trick?
The first idea would be to try to find some equivalent to the destested element . For context-dependant optimiser such as better-than-average, there isn’t.
A more general way to try to generalize the trick would be the following question:
For some fixed , and , could we find some other such as and
i.e. is there a general way to replace values outside of without modify the result of the constrained optimisation?
Answer: no. Counter-example: The optimiser for some infinite set X and finite nonempty sets and R.
So it seems there is no general trick here. But why bother? We should refocus on what we mean by constrained optimisation in general, and it has nothing to do with looking for some u’. What we mean is value outside are totally irrelevant.
How? For any of the current example we have here, what we actually want is not , but : we only apply the optimiser on the legal set.
Problem: in the current formalism, an optimiser has type , so I don’t see obvious way to define the “same” optimiser on a different X. and the others here are implicitly parametrized, so it’s not that a problem, but we have to specify this. This suggests to look for categories (e.g. for argmax...).
It’s fixed ;)