Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About 'is_legacy' in config #40

Open
Changlin-Lee opened this issue Oct 30, 2024 · 1 comment
Open

About 'is_legacy' in config #40

Changlin-Lee opened this issue Oct 30, 2024 · 1 comment

Comments

@Changlin-Lee
Copy link

As shown in the training config, 'is_legacy' flag is missing, resulting 'is_legacy' is set to be True in training stage. Meanwhile, in the infer stage, 'is_legacy' is set to False in the config.

Why the training stage and infer stage is not aligned in that case?

@cornettoyu
Copy link
Collaborator

thanks for your interest. The is_legacy flag is used to distinguish the two-stage training models (as reported in the paper) and our new released models with an improved single-stage recipe. The training configs are only for two-stage training now and please stay tuned :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants