- Le plus récent
- Le plus de votes
- La plupart des commentaires
That violation fires when, for example, input to your endpoint has fewer columns than baseline input does. This is helpful to flag data quality issues. https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor-interpreting-violations.html
In this case, however, this is an artifact of how we perform the analysis. We concatenate output and input CSVs into a single CSV to analyze the whole thing in one go. E.g. it would look like:
output_col,input_col_1,input_col_2,...,input_col_n
In this case, however, your output has a trailing newline which means that after concatenating this looks like:
output_col # embedded newline in your output
,input_col_1,input_col_2,...,input_col_n
Triggering the code to think there is only one column in dataset and hence failing the job.
We have a fix flowing through the pipeline now, while that goes out you can add a preprocessing script to your schedule to strip out the trailing newline from the output. We will create a sample notebook for this, in the meantime docs are at https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor-pre-and-post-processing.html#model-monitor-pre-processing-script
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 8 mois