You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.
In most examples, there are two files, namely train with engine and trainer. The code is highly redundant in these two files and we should just merge them into one file.
We can add an additional flag to let the user to choose to run with either engine or trainer. As engine provides better portability from user code to colossalai-style code, we should keep engine as the default.
The text was updated successfully, but these errors were encountered:
FrankLeeeee
changed the title
Merge train_with_engine and train_with_trainer
[RFC] Merge train_with_engine and train_with_trainer
May 5, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the feature
In most examples, there are two files, namely train with engine and trainer. The code is highly redundant in these two files and we should just merge them into one file.
We can add an additional flag to let the user to choose to run with either engine or trainer. As engine provides better portability from user code to colossalai-style code, we should keep engine as the default.
The text was updated successfully, but these errors were encountered: