-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to register a model directly from pipeline? #424
Comments
@Wellington-Noberto The issue is there are child run for each pipeline run, and the output folder will be present in the child runs which run individual steps in pipeline, not in the parent run which runs the pipeline. So if you extract child runs from pipeline_run then check in those child run objects with .get_file_names() method, you will be able to see your files. Alternatively if you want to register your model, use the child run object, and not the parent run object. |
I am having a very similar issue to this where the model I create from a pipeline step doesn't appear in the directory I assumed it would - just like this issue issue. @Wellington-Noberto - did you manage to fix this and if so how? |
I'm trying to create a pipeline that can build a model of machine learning. The following code is a part of the script of the estimator step. According to the tutorial from the documentation I should save the model in the directory named 'outputs'
https://docs.microsoft.com/en-us/azure/machine-learning/service/tutorial-train-models-with-aml?view=azure-ml-py&toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpython%2Fapi%2Fazureml_py_toc%2Ftoc.json%3Fview%3Dazure-ml-py&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpython%2Fazureml_py_breadcrumb%2Ftoc.json%3Fview%3Dazure-ml-py
And then try to register the model from this folder, but the file is not being saved in this directory.
Despite that problem, what I really want is to register the model in the Workspace directly from the pipeline, instead of doing it from a local script, if possible.
The text was updated successfully, but these errors were encountered: