Skip to content

Commit ee33a4d

Browse files
authored
Merge pull request #13177 from nadaataiyab/patch-2
Updated process for operationalizing a model
2 parents 845b8d8 + f82b054 commit ee33a4d

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/machine-learning/studio/walkthrough-5-publish-web-service.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,7 @@ Our experiment should now look like this:
102102
>
103103
> It's true that the service doesn't need the original credit card data. But it does need the schema for that data, which includes information such as how many columns there are and which columns are numeric. This schema information is necessary to interpret the user's data. We leave these components connected so that the scoring module has the dataset schema when the service is running. The data isn't used, just the schema.
104104
>
105+
>One important thing to note is that if your original dataset contained the label, then the expected schema from the web input will also expect a column with the label! A way around this is to remove the label, and any other data that was in the training dataset, but will not be in the web inputs, before connecting the web input and training dataset into a common module.
105106
>
106107
107108
Run the experiment one last time (click **Run**.) If you want to verify that the model is still working, click the output of the [Score Model][score-model] module and select **View Results**. You can see that the original data is displayed, along with the credit risk value ("Scored Labels") and the scoring probability value ("Scored Probabilities".)

0 commit comments

Comments
 (0)