-
Notifications
You must be signed in to change notification settings - Fork 4
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
✨ Feast and Feast UI on the AP #3369
Comments
Note: Might be redundant if SageMaker is the chosen approach. |
Meeting to be held with the MLOps team to ascertain requirements and current state. #3372 |
This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open. |
This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you! |
Describe the feature request.
Alongside mlflow, Feast is another tool in the MLOps toolbox that allows for Data Scientists/ML practitioners to save and load 'features' for the ML models. Features act slightly differently to how we currently treat 'data' on the AP. In addition, Feast has its own UI so users can explore models and features, allowing for better collaboration between ML projects.
Describe the context.
I am starting my role as MLOps coordinator from next week. Therefore I am highlighting MLOps needs as early as possible in the hopes that they can be made possible during my six month stint.
Value / Purpose
Without a dedicated tool like Feast, the impact of Data Science at MoJ will be greatly reduced. It will save time for the Data Scientists by providing a centralised store of their own features, but also provide them with the opportunity to see what others are doing. Without this approach, ML model features will not be easily transferrable across ML projects.
User Types
Data Scientists doing ML
The text was updated successfully, but these errors were encountered: