ESPnet2 To ESPnet3 Migration
Less than 1 minute
ESPnet2 To ESPnet3 Migration
The main migration shift is:
- ESPnet2: shell-driven recipes and stage numbers
- ESPnet3: Python
run.py,Systemmethods, YAML-first configs
Current ESPnet3 naming
Use:
training.yamlinference.yamlmetrics.yamlpublication.yaml
and stages:
create_datasetcollect_statstraininfermeasurepack_modelupload_model
Dataset migration
Recipe-local dataset integration should now center on:
dataset/__init__.pydataset/builder.pydataset/dataset.py
not on the older src/create_dataset.py / src/dataset.py framing as the main integration story.
Practical migration checklist
- copy
egs3/TEMPLATE/<system>/ - move config naming to
training.yaml,inference.yaml,metrics.yaml,publication.yaml - port data preparation into
DatasetBuilder - port dataset loading into
Dataset - update
run.pyto use current config flags - update inference and measurement to
infer+measure
