Skip to content

Conversation

@tcare
Copy link
Contributor

@tcare tcare commented Feb 28, 2020

To address feedback about some confusion when following the guide (especially to do with service connections) I have refactored the document structure.

  • Optional tasks / extra info has been moved down to either 'Further Exploration' (directly for getting started) or 'Next Steps' (specifically for integrating ML code.)
  • Grammar fixes and simplified wording in parts
  • Removed manual word wrapping to let autoformat do its thing
  • Added a table of contents

@tcare tcare requested review from dtzar and eedorenko February 28, 2020 19:49
Copy link
Contributor

@dtzar dtzar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restructure looks good overall!

* The second stage of the pipeline, **Train model**, triggers the run of the ML Training Pipeline. The training pipeline will train, evaluate, and register a new model. The actual computation is performed in an [Azure Machine Learning Compute cluster](https://docs.microsoft.com/en-us/azure/machine-learning/service/how-to-set-up-training-targets#amlcompute). In Azure DevOps, this stage runs an agentless job that waits for the completion of the Azure ML job, allowing the pipeline to wait for training completion for hours or even days without using agent resources.

**Note:** If the model evaluation determines that the new model does not perform better than the previous one then the new model will not be registered and the pipeline will be cancelled.
**Note:** If the model evaluation determines that the new model does not perform better than the previous one, the new model will not be registered and the pipeline will be cancelled.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the step which will fail, the error message, and possibly the link in the evaulate code too, so we don't get another issue filed on this topic.

@tcare tcare force-pushed the tcare/gs-refactor branch from 47ed406 to 7a7f741 Compare February 29, 2020 00:17
@tcare tcare force-pushed the tcare/gs-refactor branch from 6461be2 to c91baa4 Compare March 2, 2020 20:51
@tcare tcare removed the request for review from eedorenko March 3, 2020 20:08
@tcare tcare merged commit e856a4f into master Mar 3, 2020
@tcare tcare deleted the tcare/gs-refactor branch March 3, 2020 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants