Debugging non-terminal dataset errors
The following are non-terminal errors that can occur during dataset creation or update. These errors can invalidate an entire JSON Line or invalidate annotations within a JSON Line. If a JSON Line has an error, it is not used for training. If an annotation within a JSON Line has an error, the JSON Line is still used for training, but without the broken annotation. For more information about JSON Lines, see Creating a manifest file.
You can access non-terminal errors from the console and by calling the ListDatasetEntries API.
For more information, see Listing dataset entries (SDK).
The following errors are are also returned during training. We recommend that you fix these errors before training your model.For more information, see Non-Terminal JSON Line Validation Errors.
Accessing non-terminal errors
You can use the console to find out which images in a dataset have non-terminal errors.
You can also call, call ListDatasetEntries API to get the error messages.
For more information, see Listing dataset entries (SDK).
To access non-terminal errors(console)
Open the Amazon Rekognition console at https://console.aws.amazon.com/rekognition/
. Choose Use Custom Labels.
Choose Get started.
In the left navigation pane, choose Projects.
In the Projects page, choose the project that you want to use. The details page for your project is displayed.
If you want to view non-terminal errors in your training dataset, choose the Training tab. Otherwise choose the Test tab to view non-terminal errors in your test dataset.
In the Labels section of the dataset gallery, choose Errors. The dataset gallery is filtered to only show images with errors.
Choose Error underneath an image to see the error code. Use the information at Non-Terminal JSON Line Validation Errors to fix the error.
