Skip to content
#

azureml

Here are 54 public repositories matching this topic...

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

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

You can’t perform that action at this time.