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

[ML-aware Architecture] Definition of the ML pipeline #127

Open
fwilhelmi opened this issue Jul 16, 2019 · 1 comment
Open

[ML-aware Architecture] Definition of the ML pipeline #127

fwilhelmi opened this issue Jul 16, 2019 · 1 comment

Comments

@fwilhelmi
Copy link
Member

In order to execute the ML functionalities at the corresponding nodes/entities, the ML pipeline must be defined. Moreover, we must provide a clean separation of ML functionalities to be executed through the ML pipeline.

In Komondor, the ML pipeline will be defined at both agents and central controller, where different functionalities may be activated according to the use case.

@fwilhelmi fwilhelmi added this to the ML-aware Architecture milestone Jul 16, 2019
@fwilhelmi fwilhelmi self-assigned this Jul 16, 2019
@fwilhelmi
Copy link
Member Author

To do this, we need to generate abstract classes (e.g., pre-processor) and link them with the corresponding elements (e.g., AP) through pointers.

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

No branches or pull requests

1 participant