Repository navigation
[ENH] optimizer tags for accepted input types #192
Description
I think we will need tags for optimizers that tell the user - and interacting parts of the framework - what types it can accept, e.g., integer/real numbers, or string/categorical.
My suggestion would be with capability:categorical? But we probably should think carefully about this, e.g., what other tags we need, or what values can be.
Activity
amitsubhashchejara commentedon Sep 22, 2025
Hello @fkiraly, I would like to take on this issue. Could you please elaborate on this issue and assign it?
fkiraly commentedon Sep 22, 2025
@amitsubhashchejara, welcome!
I think this issue is more one for design by maintainers at the moment - you can of course also add your thoughts, though it might require familiarity with earlier design threads (sorry)
However, I opened a few new good first issues for you in case you want to take any of those: #194, #195. How about these? These have a clear specification.
fkiraly commentedon Sep 22, 2025
more: #196, #197, #198
SimonBlanke commentedon Sep 27, 2025
Good idea.
capabilityis to unspecific.dimension-typesis clear. It could look like this in future versions:dimension-types: ["numeric", "categorical", "callable", "bool", "distribution", "continuous"]search-space-operations: ["union", ...]