feat: Add references to papers that use a problem - #193
#193feat: Add references to papers that use a problem#193olafmersmann wants to merge 2 commits into
Conversation
kvdblom
left a comment
There was a problem hiding this comment.
Minor comments only. If we want to make changes based on them, we can do that in new issues.
Ready to merge once decisions (and possible new issues) are made.
| title="Pareto Set Characterization in Constrained Multiobjective Optimization and the COBI Problem Generator", | ||
| authors=["Anne Auger", "Dimo Brockhoff", "Luka Opravš", "Tea Tušar"], | ||
| link={"type": "arxiv", "url": "https://arxiv.org/abs/2604.09131"}, | ||
| type="definition" |
There was a problem hiding this comment.
Could it be two (or more?) types? Like we define the problem in the paper, and use it to compare some algorithms? And if so, is that interesting enough that we would want to be able to indicate both types here?
There was a problem hiding this comment.
I guess we could turn it into a set. Thoughts from others? I don't mind either way. It's mostly a display / filtering issue for @Dvermetten.
| - dim: | ||
| max: null | ||
| min: 1 | ||
| type: categorical |
There was a problem hiding this comment.
Just a reminder that the non-deterministic ordering for these generated files is very annoying when reviewing. We should (somewhat) prioritise fixing that. (We should make a new issue for that if we don't have one yet.)
|
@olafmersmann Just a reminder to check my comments. Once decided/handled this can be merged. |
Add a
typefield to references which can take the following values:"definition": Defines or introduces a new thing (problem, algorithm, features, ...)"use": Uses a problem"critique": Discussed the suitability of a problem for some task or fieldUpdates the examples in the
examples/subdirectory andproblems.yamlaccordingly.