Enh: move train and eval scripts to methods, pip package

Currently train.py and eval.py are implemented as scripts. This causes some problems when interfacing YOLACT from python.

I’d like to propose changing from separate script files (the scripts can still exist for convenience) to more OOP approach and having train(), eval() as part of the Yolact class.

This would allow us to make a pip package for this repo for much easier integration in other projects (currently I suffer with git submodules)

[breznak]

@dbolya do you have some WIP on this? If not, I’d start atleast a small bits of this. We need yolact to be used as a pip package and from another code, ideally.

[dbolya]

Hmm, the issue is there’s a lot of global set up stuff that goes on since I never intended you to be able to call train() from outside of train.py. I’ll see to what extent I have to modify the code to remove all the global stuff.

As for running the model externally (outside of eval.py), yeah I agree that should be top priority as there’s a lot of set up involved currently: see #256.

The eval pipeline doesn’t have a lot of global side effects though (only 2 changes required according to the last comment in that issue), so that should be easier. Onto the TODO list it goes.