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

Split nn.py #172

Closed
wants to merge 2 commits into from
Closed

Split nn.py #172

wants to merge 2 commits into from

Conversation

Atticus1806
Copy link
Contributor

Prequesite for #151

Refactoring was done by @christophmluscher

use_python_control: Optional[bool]


NnTrainingArgs = ReturnnRasrTrainingArgs # Legacy compatibility
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name ReturnnRasrTrainingArgs is already used in data, this is very confusing if the same name appears twice with a superset of parameters and (possibly?) different usage.

@christophmluscher



@dataclass()
class NnRecogArgs:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same class appearing twice? This can not be correct. I assume we can just delete the first version then?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is marked Todo by @christophmluscher so maybe he can give more information on the thoughts here / how to proceed

@christophmluscher
Copy link
Contributor

I created my own PR. Syncing with @Atticus1806 PR was annoying...

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

Successfully merging this pull request may close these issues.

3 participants