Open m-philipps opened 1 year ago
Is this the desired behaviour? If so I would add an informative Warning when there are failed starts in the start_indices
. If not, I could use the delete_nan_inf
function for all start_indices
options
Is this the desired behaviour?
No, I don't think so.
Yeah, some warning "Skipping result {id/idx} due to non-finite / missing parameter values" would make sense.
closed until reproduced
Reproducing the bug is fairly straightforward with an optimisation result with any failed start, i.e. fval = inf
and x = None
.
The issue is that the list of parameter vectors are converted to a numpy array before filtering out None
and and the function for that, delete_nan_inf
, assumes them to be a numpy array.
This appears to be specific to the way that each optimiser returns the values for x.
Bug description
visualize.parameters
fails withValueError
when some of the optimization starts failed, i.e.result.optimize_result[i]['x']
isNone
:Expected behavior I would expect the parameters plot to be generated without the failed starts
Comment In the lower level process_start_indices
delete_nan_inf
is only used whenstart_indices
is set to'all_clustered'
or'first_cluster'