111 create yaml template for problem submission #121
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| # Please enter the relevant information. | ||
| # Fields that are not relevant can be left empty. | ||
| - name: | ||
| short: BBOB | ||
| full: Real-Parameter Black-Box Optimization Benchmarking | ||
| suite/generator/single: suite | ||
|
Collaborator
There was a problem hiding this comment. I still think it would be best to enter problems separately, but I understand the necessity of streamlining this process. So if we want to allow entering suites, maybe we have different templates? Because some values might only make sense for a suite? Otherwise, for a suite, a lot of the input would be "varies" for number of objectives, variables, constraints, dynamic, noise, etc? |
||
| objectives: | ||
| number: '1' | ||
|
Collaborator
There was a problem hiding this comment. Could this also be scalable? And why is this a string? |
||
| types: single | ||
|
Collaborator
There was a problem hiding this comment. I would have assumed "types" is continuous etc? What does "single" mean? |
||
| variables: | ||
| types: continuous | ||
| conditional: 'no' | ||
| dimensionality: scalable | ||
| constraints: | ||
| present: 'no' | ||
|
Collaborator
There was a problem hiding this comment. This is confusing to enter, because they have boundary/box: yes. |
||
| soft: '0' | ||
| hard: '0' | ||
| boundary/box: 'yes' | ||
| permutation: 'no' | ||
| dynamic: | ||
| present: 'no' | ||
| types: '' | ||
| noise: 'no' | ||
| modality: | ||
| types: 'unimodal, multimodal' | ||
| evaluations: | ||
| multi-fidelity: 'no' | ||
| partial possible: 'no' | ||
| independent objectives: 'no' | ||
| reference: | ||
| links: | ||
| - https://doi.org/10.1080/10556788.2020.1808977 | ||
| authors: '' | ||
|
|
||
| contact person: '' | ||
| implementations: | ||
| - name: COCO | ||
| link: https://github.com/numbbo/coco | ||
| languges: 'C, Python' | ||
|
Collaborator
There was a problem hiding this comment. Technically, COCO has way more interfaces. |
||
| evaluation time: 'less than a second' | ||
|
Collaborator
There was a problem hiding this comment. This is going to be wild to analyse if we don't give some structure |
||
| specific requirements: 'no' | ||
|
Collaborator
There was a problem hiding this comment. what would be an example of a specific requirement? |
||
| source: | ||
| real-world: | ||
|
Collaborator
There was a problem hiding this comment. What are degree and open/closed? |
||
| degree: '' | ||
| open/closed: '' | ||
| artificial: 'yes' | ||
| other: 'no' | ||
| textual description: | ||
| general info: '' | ||
| motivation: 'evaluate algorithm performance for typical difficulties that occur in continuous problems' | ||
| challenage/key characteristics: '' | ||
|
|
||
| limitations: '' | ||
| other info: '' | ||
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.
Can I not just remove the field?