-
Notifications
You must be signed in to change notification settings - Fork 89
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
NLP summarization pipeline #43
Conversation
* Adding the steps for data registration as MLTable * Adding the steps for using AutoML for NLP
This pull request introduces 8 alerts when merging a3cc52f into 29e6a1a - view on LGTM.com new alerts:
|
This pull request introduces 8 alerts when merging 6ee3186 into 29e6a1a - view on LGTM.com new alerts:
|
This pull request introduces 8 alerts when merging b06ca77 into f4327f6 - view on LGTM.com new alerts:
|
This pull request introduces 8 alerts when merging 654c269 into f4327f6 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 036841b into f4327f6 - view on LGTM.com new alerts:
|
|
This pull request introduces 8 alerts when merging 68b5f45 into 7f0a46b - view on LGTM.com new alerts:
|
PR into Azure/mlops-v2
Checklist
I have:
Changes
Overview
The pipeline consists in fine tuning a summarization model on pubmed, then comparing its metrics with a baseline model (not fine tuned). If the comparison is successful, then the model gets registered officially as a Model in AzureML.