-
Notifications
You must be signed in to change notification settings - Fork 196
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
fix bug for evaluating noise automatically for redundants points with noisy output when the inputs are mixed categorical #509
Conversation
smt/surrogate_models/krg_based.py
Outdated
@@ -435,6 +435,18 @@ def _new_train(self): | |||
if not self.options["eval_noise"]: | |||
self.optimal_noise = np.array(self.options["noise0"]) | |||
elif self.options["use_het_noise"]: | |||
X = self.training_points[None][0][0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
X
and y
seems to be already set at the beginning of the function and the standardization seems to be done just above. I understand there are side-effects on X above but It is quite difficult to understand the flow between mixed-variables stuff and noise management. Maybe you should add comments to explain what is going on with X and y. And how mixed-variables and noise management are related. Does it make sense to have noise on a discrete variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The noise is either global (noise0) and can be estimated automatically (eval_noise) or it is point-wise (hétéroscedastic) and given. It do not depends on the nature of the variables.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so my question is why do you set X and y again and standardize again? Seems like mixed-variable handling above has an impact here otherwise this is already done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll update on that to change the standardization position and rename variables that are different!
No description provided.