Illegal value for the frequent floating precision issue about configspace HOT 3 CLOSED

Hmmm, while in principal I agree, it opens the door for what is close, i.e. should all Float parameters then also accept a tolerance?

from configspace.

In my use case, i.e. YAHPO, I just use the np.isclose with the default tolerance and if it's slightly out of the range, I clip the value.
Ofc, you cannot easily define what "close" means, but some packages seem to be affected by sampling from boundaries.
In that sense, all float parameters need to be (somehow) modified (optionally with warning).

from configspace.

Just revisited this after finisihng #346. I think there's too many places where this isclose check would introduce difficulties in value space. However we do make use of isclose in vectorized space.

I'll close this with the statement that numbers provided in value space (as opposed to vectorized space) are given by the user and as such have the ability to choose their tolerance and what they'd like to do. However if you encounter issues like this in vectorized space, then please do raise another issue!

from configspace.