Skip to content

Consistent speech model input names for the Seq2SeqTrainer generate function #13825

Closed
@OllieBroadhurst

Description

🚀 Feature request

Could we maybe have a consistent naming convention for speech models? So far we have:

From what I can tell, these are mostly the same for the purposes of how the Seq2SeqTrainer interprets them.

Motivation

This would prevent the need for custom Seq2SeqTrainer classes and would make training more modular.

Your contribution

A change in param names would do the trick but could break a lot of code. Alternatively adding the capability to accept different key values in the generate function here would work too using a (clunky) mapping such as INPUT_MAPPING_LABELS = {"input_features": "input_ids", "input_values": "input_ids", "input_ids": "input_ids"}.

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions