Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

[FEA] Include handling of categorical features in the anomaly detection component. #284

Open
tzemicheal opened this issue Nov 9, 2020 · 4 comments
Assignees

Comments

@tzemicheal
Copy link
Contributor

tzemicheal commented Nov 9, 2020

Is your feature request related to a problem? Please describe.
Add a method of splitting for a categorical features using bag sampling approach for tree based anomaly detection. Customize the node splitting to handle IP address, port, protocol … etc.

Additional context
This implementation will have dependencies on ExtraTreeRegression implementation of CuML.

@tzemicheal tzemicheal added the feature request New feature or request label Nov 9, 2020
@tzemicheal tzemicheal changed the title [FEA] Include handling categorical features in the anomaly detection module. [FEA] Include handling of categorical features in the anomaly detection component. Nov 9, 2020
@github-actions
Copy link

This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@tzemicheal
Copy link
Contributor Author

tzemicheal commented Feb 22, 2021

This has dependency on this feature request rapidsai/cuml#3063

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: No status
Development

No branches or pull requests

1 participant