-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
nnet3- small task #55
Comments
Taken. |
thanks.. On Wed, Aug 5, 2015 at 5:06 PM, Kirill Katsnelson notifications@github.com
|
kkm000
pushed a commit
to kkm000/kaldi
that referenced
this issue
Aug 6, 2015
…optimizations turned off one by one.
PR in a sec. |
kkm000
pushed a commit
to kkm000/kaldi
that referenced
this issue
Aug 6, 2015
…optimizations turned off one by one.
danpovey
added a commit
that referenced
this issue
Aug 6, 2015
Resolve #55: Retry nnet3/nnet-optimize-test on failure with optimizations turned off one by one.
galv
pushed a commit
to galv/kaldi
that referenced
this issue
Dec 10, 2022
Resolve "Accelerate CI/CD" Closes kaldi-asr#55 See merge request dl/dgx/kaldi!112
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This task is for anyone who can do it and has free time.
If you check out the nnet3 branch of the code and build it, you'll notice that there is a test failure in nnet3-optimize-test:
LOG (UnitTestNnetOptimize():nnet-optimize-test.cc:111) Output sum (not optimized) is -33558.6
LOG (UnitTestNnetOptimize():nnet-optimize-test.cc:113) Output sum (optimized) is -34012.6
ERROR (UnitTestNnetOptimize():nnet-optimize-test.cc:115) Non-optimized and optimized versions of the computation give different outputs.
terminate called after throwing an instance of 'std::runtime_error'
what(): ERROR (UnitTestNnetOptimize():nnet-optimize-test.cc:115) Non-optimized and optimized versions of the computation give different outputs.
[stack trace: ]
kaldi::KaldiGetStackTrace()
kaldi::KaldiErrorMessage::~KaldiErrorMessage()
kaldi::nnet3::UnitTestNnetOptimize()
./nnet-optimize-test(main+0xe3) [0x54903b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f3de3f45ead]
./nnet-optimize-test() [0x547b69]
What needs to be done is a refactoring and change to UnitTestNnetOptimize(), so that when it detects a mismatch like this, it will turn on the optimizations in the NnetOptimizeOptions config one by one and show the output-sum for each one separately, and hopefully, as a convenience, try to inform the user which of those optimizations seems to be the issue.
Vijay was going to do this but he is very busy right now and I thought it's the kind of thing we could find someone from the list to do.
Dan
The text was updated successfully, but these errors were encountered: