How can we improve Microsoft Azure Machine Learning?

Re-open feature request "Deployment of ML experiments programmatically"

This feature request is marked as complete https://feedback.azure.com/forums/257792-machine-learning/suggestions/7575534-deployment-of-ml-experiments-programmatically, but the library is still far from being complete.

In https://github.com/hning86/azuremlps#import-amlexperimentgraph, we see the following note:

"Please note that the exported JSON file only contains references to the exact instance and version of the assets (modules, trained models, datasets, etc.). The assets themselves are NOT serialized into the JSON file. As a consequence, when you import it back into the Workspace, unless you are importing it back into the same Workspace, or unless your graph only contains global assets such as built-in modules, you will not be able to create a valid Experiment. And you might see the Studio UX crashes when attempting to open this invalid experiment. In other words, importing an exported graph that contains user datasets, trained models, custom modules, etc. into a new workspace will not work. Also, please make sure you use absolute path when referring to the json file."

Importing an experiment to a *different* workspace is *essential* for automatic deployment, but is not possible for the reasons described in the documentation. This needs to be fixed before the feature can really be considered to be complete.

0 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christos KarrasChristos Karras shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Christos KarrasChristos Karras commented  ·   ·  Flag as inappropriate

        Note that if there are limitations that prevent implementing this in AMLPS, it should be fixed directly in AzureML.

      Feedback and Knowledge Base