-
Notifications
You must be signed in to change notification settings - Fork 223
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
Add protect method for feature order in fl-xgb #497
Conversation
min_value = min(data[feature_order_frame][:, i]) | ||
max_value = max(data[feature_order_frame][:, i]) | ||
if j == 0: | ||
self.split_value[i][idx_end] = max_value |
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 value on the right hand side should be divided by 2.0
federatedscope/vertical_fl/trainer/feature_order_protected_trainer.py
Outdated
Show resolved
Hide resolved
'extra_info': extra_info | ||
} | ||
|
||
def _get_feature_order_info(self, data): |
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.
For convenience, I also protected the label owner's feature order before. Actually, label owner does not need to do this.
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.
Since it need some more efforts to fix this issue such as modifying the split position accordingly, we can add TODO item here and fix it later
federatedscope/vertical_fl/xgb_base/baseline/xgb_base_on_blogfeedback.yaml
Show resolved
Hide resolved
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.
Good job!
Thanks a lot for the co-contributor @qbc2016, and sorry the mess commits due to the squash merge of #482