Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Number Shift in the resulting Dataframe #1

Open
yannickfunk opened this issue May 21, 2019 · 2 comments
Open

Number Shift in the resulting Dataframe #1

yannickfunk opened this issue May 21, 2019 · 2 comments

Comments

@yannickfunk
Copy link

I specified the following parameter Space and ran the Optunity Solver:
config = {
"hyperparameter": {
"convlayers": {
"domain": "uniform",
"data": [1, 5],
"type": int
},
"denselayers": {
"domain": "uniform",
"data": [1, 3],
"type": int
}
}
For every run recorded in the Pandas Dataframe the Index of the number is displayed, not the actual number. For example convlayers: 0, but should be convlayers: 1 and so on. I think it is preferable to store the actual integer number

@rfloca
Copy link
Contributor

rfloca commented May 22, 2019

Hi yannick,

thanks for the input. As far as I see it now, I would deem it a bug, as it breaks my expectations, because I would also expect the use hyper parameter value (and not propably its index on the axis).
But we have to have a closer look.

Could you do me a favor and test a nother optimizer with your setting. That would help to narrow it down (either a problem in the optunity wrapper or the hyppopy "managment" layer). Thanks.

@Maschiii
Copy link

I have a similar issue when using the Hyperopt Solver. The issue is only occuring for my hyperparameter of type 'int'. Type 'float' does not seem to be affected by this bug in my case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants