Closed DrTaDa closed 1 year ago
So this will be a change that breaks backward compatibility, right? In essence I want to avoid that all cost in BluePyOpt. I guess now it could be acceptable because I assume the use of CMA is still limited to very few people. If we do it, we should at least update the version number of bluepyopt so that the changed version could be 'easily' recognized by users when needed.
Ok. I will do that. I put the PR back as a draft because I am still investigating if these changes are really worth it.
Not relevant anymore
The goal of this PR is to avoid the over-exploration of the border of the parameter space, especially at initialisation.