Azure-docs: "azureml.explain.model._internal.application_client" module is correct?

Created on 27 Sep 2020  Â·  6Comments  Â·  Source: MicrosoftDocs/azure-docs

[Enter feedback here]
"Download engineered feature import from artifact store" section contains the following code:

from azureml.explain.model._internal.explanation_client import ExplanationClient

"azureml.explain.model._internal.application_client" module works, but is it for internal?
Is there any difference from the following?

from azureml.contrib.interpret.explanation.explanation_client import ExplanationClient
  • _Internal is also used in the sample below, is it correct?
    https://github.com/Azure/MachineLearningNotebooks/blob/master/how-to-use-azureml/automated-machine-learning/regression-explanation-featurization/auto-ml-regression-explanation-featurization.ipynb

    from azureml.interpret._internal.explanation_client import ExplanationClient
    

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 assigned-to-author corsubsvc machine-learninsvc product-question triaged

Most helpful comment

@nibaccam Minsoo completed this PR this week: https://github.com/MicrosoftDocs/azure-docs-pr/pull/131579/files

All 6 comments

@damochiz, Thank you for reaching out. We are looking into this and will get back to you soon.

@damochiz All the import scenarios point to the same ExplanationClient but the future releases of the SDK will have guidance to use only the following:

from azureml.interpret import ExplanationClient

Our team is working to update the documentation with the release of new SDK version.

@luisquintanilla @Aniththa do either of you have the bandwidth for this? If not I can address when I'm back in the office 10/5

@nibaccam Minsoo completed this PR this week: https://github.com/MicrosoftDocs/azure-docs-pr/pull/131579/files

@damochiz, thanks for your report. Our team has updated the documentation, you should see the updated package import statements on the live site. I'll proceed to #please-close this issue.

Was this page helpful?
0 / 5 - 0 ratings