I would like to have an easy access to the best_solution function to be able to create new multiobjective problems with constraints where the objective and constraints are the existing BBOB functions. If/when those would be added to COCO as a new suite, they would need to be implemented in the C code anyway, so for benchmarking purposes, the Problem class interface would be used (which is "harder to abuse").
The interface doesn't match the one of the Problem class exactly because I would like an easy access to it. If this is a big issue, I can change it to match it.
I find the current access "easy enough" if you know it - but that's exactly the point that we should hide it from accidental use. Hence, I am also in favour of keeping the same interface.
I would like to have an easy access to the
best_solution
function to be able to create new multiobjective problems with constraints where the objective and constraints are the existing BBOB functions. If/when those would be added to COCO as a new suite, they would need to be implemented in the C code anyway, so for benchmarking purposes, the Problem class interface would be used (which is "harder to abuse").The interface doesn't match the one of the Problem class exactly because I would like an easy access to it. If this is a big issue, I can change it to match it.