Module aws_sdk_lookoutvision::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Lookout for Vision can respond with.
Structs§
Information about an anomaly type found on an image by an image segmentation model. For more information, see
DetectAnomalies.The description for a dataset. For more information, see
DescribeDataset.Location information about a manifest file. You can use a manifest file to create a dataset.
Statistics about the images in a dataset.
Summary information for an Amazon Lookout for Vision dataset. For more information, see
DescribeDatasetandProjectDescription.Information about the location of a manifest file that Amazon Lookout for Vision uses to to create a dataset.
The prediction results from a call to
DetectAnomalies.DetectAnomalyResultincludes classification information for the prediction (IsAnomalousandConfidence). If the model you use is an image segementation model,DetectAnomalyResultalso includes segmentation information (AnomaliesandAnomalyMask). Classification information is calculated separately from segmentation information and you shouldn't assume a relationship between them.Configuration information for the AWS IoT Greengrass component created in a model packaging job. For more information, see
StartModelPackagingJob.You can't specify a component with the same
ComponentNameandComponentversionas an existing component with the same component name and component version.Information about the AWS IoT Greengrass component created by a model packaging job.
The source for an image.
Amazon S3 Location information for an input manifest file.
Describes an Amazon Lookout for Vision model.
Describes an Amazon Lookout for Vision model.
Configuration information for a Amazon Lookout for Vision model packaging job. For more information, see
StartModelPackagingJob.Information about a model packaging job. For more information, see
DescribeModelPackagingJob.Metadata for a model packaging job. For more information, see
ListModelPackagingJobs.Information about the output from a model packaging job.
Information about the evaluation performance of a trained model.
The S3 location where Amazon Lookout for Vision saves model training files.
The S3 location where Amazon Lookout for Vision saves training output.
Information about the pixels in an anomaly mask. For more information, see
Anomaly.PixelAnomalyis only returned by image segmentation models.Describe an Amazon Lookout for Vision project. For more information, see
DescribeProject.Metadata about an Amazon Lookout for Vision project.
Information about the location of training output or the output of a model packaging job.
A key and value pair that is attached to the specified Amazon Lookout for Vision model.
The platform on which a model runs on an AWS IoT Greengrass core device.
Enums§
- When writing a match expression against
DatasetStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ModelHostingStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ModelPackagingJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ModelStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetDevice, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetPlatformAccelerator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetPlatformArch, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetPlatformOs, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.