#[non_exhaustive]pub struct AutoMlCandidateGenerationConfig {
pub feature_specification_s3_uri: Option<String>,
pub algorithms_config: Option<Vec<AutoMlAlgorithmConfig>>,
}
Expand description
Stores the configuration information for how a candidate is generated (optional).
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.feature_specification_s3_uri: Option<String>
A URL to the Amazon S3 data source containing selected features from the input data source to run an Autopilot job. You can input FeatureAttributeNames
(optional) in JSON format as shown below:
{ "FeatureAttributeNames":\["col1", "col2", ...\] }
.
You can also specify the data type of the feature (optional) in the format shown below:
{ "FeatureDataTypes":{"col1":"numeric", "col2":"categorical" ... } }
These column keys may not include the target column.
In ensembling mode, Autopilot only supports the following data types: numeric
, categorical
, text
, and datetime
. In HPO mode, Autopilot can support numeric
, categorical
, text
, datetime
, and sequence
.
If only FeatureDataTypes
is provided, the column keys (col1
, col2
,..) should be a subset of the column names in the input data.
If both FeatureDataTypes
and FeatureAttributeNames
are provided, then the column keys should be a subset of the column names provided in FeatureAttributeNames
.
The key name FeatureAttributeNames
is fixed. The values listed in \["col1", "col2", ...\]
are case sensitive and should be a list of strings containing unique values that are a subset of the column names in the input data. The list of columns provided must not include the target column.
algorithms_config: Option<Vec<AutoMlAlgorithmConfig>>
Stores the configuration information for the selection of algorithms trained on tabular data.
The list of available algorithms to choose from depends on the training mode set in TabularJobConfig.Mode
.
-
AlgorithmsConfig
should not be set if the training mode is set onAUTO
. -
When
AlgorithmsConfig
is provided, oneAutoMLAlgorithms
attribute must be set and one only.If the list of algorithms provided as values for
AutoMLAlgorithms
is empty,CandidateGenerationConfig
uses the full set of algorithms for the given training mode. -
When
AlgorithmsConfig
is not provided,CandidateGenerationConfig
uses the full set of algorithms for the given training mode.
For the list of all algorithms per problem type and training mode, see AutoMLAlgorithmConfig.
For more information on each algorithm, see the Algorithm support section in Autopilot developer guide.
Implementations§
Source§impl AutoMlCandidateGenerationConfig
impl AutoMlCandidateGenerationConfig
Sourcepub fn feature_specification_s3_uri(&self) -> Option<&str>
pub fn feature_specification_s3_uri(&self) -> Option<&str>
A URL to the Amazon S3 data source containing selected features from the input data source to run an Autopilot job. You can input FeatureAttributeNames
(optional) in JSON format as shown below:
{ "FeatureAttributeNames":\["col1", "col2", ...\] }
.
You can also specify the data type of the feature (optional) in the format shown below:
{ "FeatureDataTypes":{"col1":"numeric", "col2":"categorical" ... } }
These column keys may not include the target column.
In ensembling mode, Autopilot only supports the following data types: numeric
, categorical
, text
, and datetime
. In HPO mode, Autopilot can support numeric
, categorical
, text
, datetime
, and sequence
.
If only FeatureDataTypes
is provided, the column keys (col1
, col2
,..) should be a subset of the column names in the input data.
If both FeatureDataTypes
and FeatureAttributeNames
are provided, then the column keys should be a subset of the column names provided in FeatureAttributeNames
.
The key name FeatureAttributeNames
is fixed. The values listed in \["col1", "col2", ...\]
are case sensitive and should be a list of strings containing unique values that are a subset of the column names in the input data. The list of columns provided must not include the target column.
Sourcepub fn algorithms_config(&self) -> &[AutoMlAlgorithmConfig]
pub fn algorithms_config(&self) -> &[AutoMlAlgorithmConfig]
Stores the configuration information for the selection of algorithms trained on tabular data.
The list of available algorithms to choose from depends on the training mode set in TabularJobConfig.Mode
.
-
AlgorithmsConfig
should not be set if the training mode is set onAUTO
. -
When
AlgorithmsConfig
is provided, oneAutoMLAlgorithms
attribute must be set and one only.If the list of algorithms provided as values for
AutoMLAlgorithms
is empty,CandidateGenerationConfig
uses the full set of algorithms for the given training mode. -
When
AlgorithmsConfig
is not provided,CandidateGenerationConfig
uses the full set of algorithms for the given training mode.
For the list of all algorithms per problem type and training mode, see AutoMLAlgorithmConfig.
For more information on each algorithm, see the Algorithm support section in Autopilot developer guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .algorithms_config.is_none()
.
Source§impl AutoMlCandidateGenerationConfig
impl AutoMlCandidateGenerationConfig
Sourcepub fn builder() -> AutoMlCandidateGenerationConfigBuilder
pub fn builder() -> AutoMlCandidateGenerationConfigBuilder
Creates a new builder-style object to manufacture AutoMlCandidateGenerationConfig
.
Trait Implementations§
Source§impl Clone for AutoMlCandidateGenerationConfig
impl Clone for AutoMlCandidateGenerationConfig
Source§fn clone(&self) -> AutoMlCandidateGenerationConfig
fn clone(&self) -> AutoMlCandidateGenerationConfig
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for AutoMlCandidateGenerationConfig
impl PartialEq for AutoMlCandidateGenerationConfig
Source§fn eq(&self, other: &AutoMlCandidateGenerationConfig) -> bool
fn eq(&self, other: &AutoMlCandidateGenerationConfig) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for AutoMlCandidateGenerationConfig
Auto Trait Implementations§
impl Freeze for AutoMlCandidateGenerationConfig
impl RefUnwindSafe for AutoMlCandidateGenerationConfig
impl Send for AutoMlCandidateGenerationConfig
impl Sync for AutoMlCandidateGenerationConfig
impl Unpin for AutoMlCandidateGenerationConfig
impl UnwindSafe for AutoMlCandidateGenerationConfig
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);