Skip to content

Commit b8020d2

Browse files
jr-MSmrbullwinkle
andauthored
Update articles/cognitive-services/Anomaly-Detector/overview-multivariate.md
Co-authored-by: Michael <[email protected]>
1 parent c747d94 commit b8020d2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cognitive-services/Anomaly-Detector/overview-multivariate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Basically, Multivariate Anomaly Detector includes three main steps, **data prepa
3838
For data preparation, you should prepare two parts of data, **training data** and **inference data**. As for training data, you should upload your data to Blob Storage and generate an SAS url which will be used in training API. As for inference data, you could either use the same data format as training data, or send the data into API header which will be a json format. This depends on what API you would use in inference process.
3939

4040
### Training
41-
When training a model, you should call an asynchronized API on your training data, which means you won't get the model status immediately after calling this API, you should requessf jjsfd jijisjist another API to get the model status.
41+
When training a model, you should call an asynchronized API on your training data, which means you won't get the model status immediately after calling this API, you should request another API to get the model status.
4242

4343
### Inference
4444
In inference process, you have two options to choose, asynchroized API or synchronized API. If you would like to do a batch validation, you are suggested to use asynchronized API. If you want to do streaming in a short granularity and get the inference result immediately after each API request, you are suggested to use synchronized API.

0 commit comments

Comments
 (0)