0.25.0 (2025-12-11)
Adds full support for non-square image sizes with CLI parsing, data/augmentation/mappers/processors updates, inference/export benchmarking changes, and docs/examples; also updates AutoDataset.get_split to accept DatasetAugmentations.
- Image size handling (core):
- Make
ModelInfo.im_sizeacceptint | (H, W); propagate throughTrainerArgs, processors, mappers, and ports. - Update processors (
DETR,RTMO,MaskFormer,BisenetFormer,Classification) to accept tuple sizes and resize accordingly.
- Make
- Adjust inference runtimes (ONNX, TorchScript, base model) warmup/benchmark to support non-square and log proper size; set latency
im_sizeusing height. - CLI:
- Add
parse_im_sizeto accept"640","640,480", or"640x480". - Change
train,val, andexport--im-sizeoption to string, parse toint | (H, W)and pass through.
- Add
- Data pipeline:
DatasetAugmentations.resolutionnowint | (H, W); non-square uses directResize, square keepsResizeShortestEdge; adjust crop to use absolute size.get_default_by_taskand all call sites now pass/returnDatasetAugmentations(not raw list).AutoDataset.get_split(augs=...)now expectsDatasetAugmentationsand forwards both augs andresolution; remove.get_augmentations()usage across code/tests/tutorials.- Mappers carry
resolution;MapDatasetexposesresolutionproperty.
- Export/Training:
export_commandand model export accept tuple sizes; setmodel_info.im_sizeto the provided resolution.- After training, always reload best model/info and set model/processor to eval.
- Docs:
- Update README and docs (CLI, concepts, inference, training) with non-square examples and usage notes.
What's Changed
- feat: enhance image size handling across the codebase by @CuriousDolphin in #167
Full Changelog: v0.24.0...v0.25.0