#[non_exhaustive]pub struct TimeSeriesForecastingJobConfig {
pub feature_specification_s3_uri: Option<String>,
pub completion_criteria: Option<AutoMlJobCompletionCriteria>,
pub forecast_frequency: Option<String>,
pub forecast_horizon: Option<i32>,
pub forecast_quantiles: Option<Vec<String>>,
pub transformations: Option<TimeSeriesTransformations>,
pub time_series_config: Option<TimeSeriesConfig>,
pub holiday_config: Option<Vec<HolidayConfigAttributes>>,
pub candidate_generation_config: Option<CandidateGenerationConfig>,
}
Expand description
The collection of settings used by an AutoML job V2 for the time-series forecasting problem type.
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 additional selected features that complement the target, itemID, timestamp, and grouped columns set in TimeSeriesConfig
. When not provided, the AutoML job V2 includes all the columns from the original dataset that are not already declared in TimeSeriesConfig
. If provided, the AutoML job V2 only considers these additional columns as a complement to the ones declared in TimeSeriesConfig
.
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" ... } }
Autopilot supports the following data types: numeric
, categorical
, text
, and datetime
.
These column keys must not include any column set in TimeSeriesConfig
.
completion_criteria: Option<AutoMlJobCompletionCriteria>
How long a job is allowed to run, or how many candidates a job is allowed to generate.
forecast_frequency: Option<String>
The frequency of predictions in a forecast.
Valid intervals are an integer followed by Y (Year), M (Month), W (Week), D (Day), H (Hour), and min (Minute). For example, 1D
indicates every day and 15min
indicates every 15 minutes. The value of a frequency must not overlap with the next larger frequency. For example, you must use a frequency of 1H
instead of 60min
.
The valid values for each frequency are the following:
-
Minute - 1-59
-
Hour - 1-23
-
Day - 1-6
-
Week - 1-4
-
Month - 1-11
-
Year - 1
forecast_horizon: Option<i32>
The number of time-steps that the model predicts. The forecast horizon is also called the prediction length. The maximum forecast horizon is the lesser of 500 time-steps or 1/4 of the time-steps in the dataset.
forecast_quantiles: Option<Vec<String>>
The quantiles used to train the model for forecasts at a specified quantile. You can specify quantiles from 0.01
(p1) to 0.99
(p99), by increments of 0.01 or higher. Up to five forecast quantiles can be specified. When ForecastQuantiles
is not provided, the AutoML job uses the quantiles p10, p50, and p90 as default.
transformations: Option<TimeSeriesTransformations>
The transformations modifying specific attributes of the time-series, such as filling strategies for missing values.
time_series_config: Option<TimeSeriesConfig>
The collection of components that defines the time-series.
holiday_config: Option<Vec<HolidayConfigAttributes>>
The collection of holiday featurization attributes used to incorporate national holiday information into your forecasting model.
candidate_generation_config: Option<CandidateGenerationConfig>
Stores the configuration information for how model candidates are generated using an AutoML job V2.
Implementations§
Source§impl TimeSeriesForecastingJobConfig
impl TimeSeriesForecastingJobConfig
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 additional selected features that complement the target, itemID, timestamp, and grouped columns set in TimeSeriesConfig
. When not provided, the AutoML job V2 includes all the columns from the original dataset that are not already declared in TimeSeriesConfig
. If provided, the AutoML job V2 only considers these additional columns as a complement to the ones declared in TimeSeriesConfig
.
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" ... } }
Autopilot supports the following data types: numeric
, categorical
, text
, and datetime
.
These column keys must not include any column set in TimeSeriesConfig
.
Sourcepub fn completion_criteria(&self) -> Option<&AutoMlJobCompletionCriteria>
pub fn completion_criteria(&self) -> Option<&AutoMlJobCompletionCriteria>
How long a job is allowed to run, or how many candidates a job is allowed to generate.
Sourcepub fn forecast_frequency(&self) -> Option<&str>
pub fn forecast_frequency(&self) -> Option<&str>
The frequency of predictions in a forecast.
Valid intervals are an integer followed by Y (Year), M (Month), W (Week), D (Day), H (Hour), and min (Minute). For example, 1D
indicates every day and 15min
indicates every 15 minutes. The value of a frequency must not overlap with the next larger frequency. For example, you must use a frequency of 1H
instead of 60min
.
The valid values for each frequency are the following:
-
Minute - 1-59
-
Hour - 1-23
-
Day - 1-6
-
Week - 1-4
-
Month - 1-11
-
Year - 1
Sourcepub fn forecast_horizon(&self) -> Option<i32>
pub fn forecast_horizon(&self) -> Option<i32>
The number of time-steps that the model predicts. The forecast horizon is also called the prediction length. The maximum forecast horizon is the lesser of 500 time-steps or 1/4 of the time-steps in the dataset.
Sourcepub fn forecast_quantiles(&self) -> &[String]
pub fn forecast_quantiles(&self) -> &[String]
The quantiles used to train the model for forecasts at a specified quantile. You can specify quantiles from 0.01
(p1) to 0.99
(p99), by increments of 0.01 or higher. Up to five forecast quantiles can be specified. When ForecastQuantiles
is not provided, the AutoML job uses the quantiles p10, p50, and p90 as default.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .forecast_quantiles.is_none()
.
Sourcepub fn transformations(&self) -> Option<&TimeSeriesTransformations>
pub fn transformations(&self) -> Option<&TimeSeriesTransformations>
The transformations modifying specific attributes of the time-series, such as filling strategies for missing values.
Sourcepub fn time_series_config(&self) -> Option<&TimeSeriesConfig>
pub fn time_series_config(&self) -> Option<&TimeSeriesConfig>
The collection of components that defines the time-series.
Sourcepub fn holiday_config(&self) -> &[HolidayConfigAttributes]
pub fn holiday_config(&self) -> &[HolidayConfigAttributes]
The collection of holiday featurization attributes used to incorporate national holiday information into your forecasting model.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .holiday_config.is_none()
.
Sourcepub fn candidate_generation_config(&self) -> Option<&CandidateGenerationConfig>
pub fn candidate_generation_config(&self) -> Option<&CandidateGenerationConfig>
Stores the configuration information for how model candidates are generated using an AutoML job V2.
Source§impl TimeSeriesForecastingJobConfig
impl TimeSeriesForecastingJobConfig
Sourcepub fn builder() -> TimeSeriesForecastingJobConfigBuilder
pub fn builder() -> TimeSeriesForecastingJobConfigBuilder
Creates a new builder-style object to manufacture TimeSeriesForecastingJobConfig
.
Trait Implementations§
Source§impl Clone for TimeSeriesForecastingJobConfig
impl Clone for TimeSeriesForecastingJobConfig
Source§fn clone(&self) -> TimeSeriesForecastingJobConfig
fn clone(&self) -> TimeSeriesForecastingJobConfig
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for TimeSeriesForecastingJobConfig
impl PartialEq for TimeSeriesForecastingJobConfig
Source§fn eq(&self, other: &TimeSeriesForecastingJobConfig) -> bool
fn eq(&self, other: &TimeSeriesForecastingJobConfig) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for TimeSeriesForecastingJobConfig
Auto Trait Implementations§
impl Freeze for TimeSeriesForecastingJobConfig
impl RefUnwindSafe for TimeSeriesForecastingJobConfig
impl Send for TimeSeriesForecastingJobConfig
impl Sync for TimeSeriesForecastingJobConfig
impl Unpin for TimeSeriesForecastingJobConfig
impl UnwindSafe for TimeSeriesForecastingJobConfig
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);