🚀from_config API: Create a path between API & configuration file (CLI)

[harimkang]

📝 Description

#1992

• Adds from_config ,the ability to create model and datamodule instances via the Configuration file.
• Add Engine.from_config that provide engine, model, datamodule from full-configuration files.
• Add Unit-Test for from_config features.

How to test:

1. Model & Data configuration to API Usage

# Import the required modules
from anomalib.data import AnomalibDataModule
from anomalib.engine import Engine
from anomalib.models import AnomalyModule

# Initialize the datamodule
# datamodule = MVTec()
data_config = "configs/data/mvtec.yaml"
datamodule = AnomalibDataModule.from_config(config_path=data_config)


# Initialize the model
# model = Patchcore()
model_config = "configs/model/patchcore.yaml"
model = AnomalyModule.from_config(config_path=model_config)


# Initialize engine
engine = Engine()

# Train the model
engine.fit(datamodule=datamodule, model=model)

2. Full configuration Usage (Include model, data, engine, trainer args)
   Get full configuration file (output from cli - TBD or Use --print_config > configs.yaml)

(anomalib) anomalib fit --model anomalib.models.Padim --data anomalib.data.MVTec --print_config > anomalib_config.yaml

Use Configuration file with API

from anomalib.engine import Engine

config_path = "anomalib_config.yaml"
engine, model, datamodule = Engine.from_config(config_path=config_path)
engine.fit(datamodule=datamodule, model=model)

✨ Changes

Select what type of change your PR is:

• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🔨 Refactor (non-breaking change which refactors the code base)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔒 Security update

✅ Checklist

Before you submit your pull request, please make sure you have completed the following steps:

• 📋 I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
• 📚 I have made the necessary updates to the documentation (if applicable).
• 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

For more information about code review checklists, see the Code Review Checklist.

[ashwinvaidya17]

Thanks for the efforts! I have a few minor comments. But we can also look into refactoring these later on.