Skip to content
#

azureml

Here are 79 public repositories matching this topic...

azureml-examples
dkmiller
dkmiller commented Nov 4, 2020

It would be better to add more columns to tables in README.md for easier navigation. For example, we can add the following columns:

ML framework: TF, PyTorch, LightGBM, etc.

Dataset: MNIST, Iris, etc.

Distributed or single machine

Currently README.md is automatically generated by code. Is that a good idea?

We need better organizing Tutorial notebooks. As of 11/3, the order of th

revodavid
revodavid commented Jan 26, 2020

None of the function help pages in the azuremlsdk library include a See Also section. Including relevant functions in a See Also section would help users discover functions and navigate the help system better.

Describe the solution you'd like
Add a see also section to the help pages listing relevant functions. For example, upload_files_to_datastore should refer to `download_from_datastor

In tune with conventional big data and data science practitioners’ line of thought, currently causal analysis was the only approach considered for our demand forecasting effort which was applicable across the product portfolio. Experience dictates that not all data are same. Each group of data has different data patterns based on how they were sold and supported over the product life cycle. One-methodology-fits-all is very pleasing from an implementation of view. On a practical ground, one must consider solutions for varying needs of different product types in our product portfolio like new products both evolutionary and revolutionary, niche products, high growth products and more. With this backdrop, we have evolved a solution which segments the product portfolio into quadrants and then match a series of algorithms for each quadrant instead of one methodology for all. And technology stack would be simulated/mocked data(Hadoop Ecosystem) > AzureML with R/Python > Zeppelin.

  • Updated Jul 20, 2017
  • R
Capstone-Project-Azure-Machine-Learning-Engineer

This is the Capstone project (last of the three projects) required for fulfillment of the Nanodegree Machine Learning Engineer with Microsoft Azure from Udacity. In this project, we use a dataset external to Azure ML ecosystem. Azure Machine Learning Service and Jupyter Notebook is used to train models using both Hyperdrive and Auto ML and then the best of these models is deployed as an HTTP REST endpoint. The model endpoint is also tested to verify if it is working as intented by sending an HTTP POST request. Azure ML Studio graphical interface is not used in the entire exercise to encourage use of code which is better suited for automation and gives a data scientist more control over their experiment.

  • Updated Jan 10, 2021
  • Jupyter Notebook

Improve this page

Add a description, image, and links to the azureml topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the azureml topic, visit your repo's landing page and select "manage topics."

Learn more