Buckets:

hf-doc-build/doc-dev / optimum /pr_2398 /en /utils /normalized_config.md
rtrm's picture
|
download
raw
1.96 kB

Normalized Configurations

Model configuration classes in 🤗 Transformers are not standardized. Although Transformers implements an attribute_map attribute that mitigates the issue to some extent, it does not make it easy to reason on common configuration attributes in the code. NormalizedConfig classes try to fix that by allowing access to the configuration attribute they wrap in a standardized way.

Base class[[optimum.utils.NormalizedConfig]]

While it is possible to create NormalizedConfig subclasses for common use-cases, it is also possible to overwrite the original attribute name -> normalized attribute name mapping directly using the with_args() class method.

optimum.utils.NormalizedConfig[[optimum.utils.NormalizedConfig]]

Source

Handles the normalization of PretrainedConfig attribute names, allowing to access attributes in a general way.

Parameters:

config (PretrainedConfig) : The config to normalize.

Existing normalized configurations[[optimum.utils.NormalizedTextConfig]]

optimum.utils.NormalizedTextConfig[[optimum.utils.NormalizedTextConfig]]

Source

optimum.utils.NormalizedSeq2SeqConfig[[optimum.utils.NormalizedSeq2SeqConfig]]

Source

optimum.utils.NormalizedVisionConfig[[optimum.utils.NormalizedVisionConfig]]

Source

optimum.utils.NormalizedTextAndVisionConfig[[optimum.utils.NormalizedTextAndVisionConfig]]

Source

Xet Storage Details

Size:
1.96 kB
·
Xet hash:
8e298ef94395c1faa6c9ccd7254af3922594bba4ddf4b2ebb2ea435f756e9b0c

Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.