@Juste I wanna pick up a question that has been asked earlier but hasn’t been answered yet:
Is it possible to provide components with custom data without having to hardcode file paths into the component code? (Like the example does with the “labels.txt” file).
I have a custom component that reads extra fields defined in the JSON train files, but that’s hacky and doesn’t work properly in some cases. I think one way is to define paths in the config.yml file as component configs, but that turns the config from a static pipeline definition into a training-specific data definition. Is there a better way?