This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
Register custom model / loops outside of the VISSL directory #211
Labels
enhancement
New feature or request
🚀 Feature
I would like to be able to integrate custom code, such as custom model head / trunks, or custom training loops, without having to put them directly in the vissl directory
Motivation & Examples
Like many users, I like to download my packages via pip or conda. Right now I have to manually copy my new models to the vissl directory within my environment. The main issue I have with this is that I have to manually keep track of my added files should I do a vissl update.
Note
There is already something similar already established for datasets, where I can register a new one outside of the main codebase. If there would exist something like this for models that would be great.
The text was updated successfully, but these errors were encountered: