Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GoogleCloudAiplatformV1ExplanationMetadata

import type { GoogleCloudAiplatformV1ExplanationMetadata } from "https://googleapis.deno.dev/v1/aiplatform:v1.ts";

Metadata describing the Model's input and output for explanation.

interface GoogleCloudAiplatformV1ExplanationMetadata {
featureAttributionsSchemaUri?: string;
inputs?: {
};
latentSpaceSource?: string;
outputs?: {
};
}

§Properties

§
featureAttributionsSchemaUri?: string
[src]

Points to a YAML file stored on Google Cloud Storage describing the format of the feature attributions. The schema is defined as an OpenAPI 3.0.2 Schema Object. AutoML tabular Models always have this field populated by Vertex AI. Note: The URI given on output may be different, including the URI scheme, than the one given on input. The output URI will point to a location where the user only has a read access.

§
inputs?: {
}
[src]

Required. Map from feature names to feature input metadata. Keys are the name of the features. Values are the specification of the feature. An empty InputMetadata is valid. It describes a text feature which has the name specified as the key in ExplanationMetadata.inputs. The baseline of the empty feature is chosen by Vertex AI. For Vertex AI-provided Tensorflow images, the key can be any friendly name of the feature. Once specified, featureAttributions are keyed by this key (if not grouped with another feature). For custom images, the key must match with the key in instance.

§
latentSpaceSource?: string
[src]

Name of the source to generate embeddings for example based explanations.

§
outputs?: {
}
[src]

Required. Map from output names to output metadata. For Vertex AI-provided Tensorflow images, keys can be any user defined string that consists of any UTF-8 characters. For custom images, keys are the name of the output field in the prediction to be explained. Currently only one key is allowed.