This repository was archived by the owner on Nov 17, 2023. It is now read-only.
Repository navigation
LSTM split0 Operator Error #12127
Unanswered
prathik-naidu
asked this question in
Q&A
Replies: 5 comments
|
@prathik-naidu Thanks for your issue. Please also put this issue to the discuss.mxnet.io, there are more people working on different examples. @mxnet-label-bot could you please label this as [operator, question] |
0 replies
|
@lanking520 Sure, I also just put this up on discuss.mxnet.io |
0 replies
|
EDIT: I'm reopening because I realized that even after adding in the bug fix from the above issue, the code still throws the exact same error (I was running on the wrong dataset) any reasons why this might be happening? I thought that the bug fix would work but it hasn't. |
0 replies
|
@szha here. Does this issue look like the one you fixed? |
0 replies
|
@lanking520 unfortunately no. My recent work on the RNN operator doesn't involve the split in error. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
Getting an error in the split0 operator when training an image captioning network in mxnet.
Environment info (Required)
Package used (Python/R/Scala/Julia): I'm using Python
Error Message:
Minimum reproducible example
I'm using the code from the following repository: https://github.com/saicoco/mxnet_image_caption
Everything is identical, except I use my own dataset. I've preprocessed the data identical to what this implementation expects (originally used the Flickr8k dataset).
What have you tried to solve it?
I basically need some help trying to understand where this error is coming from – in particular, why
param_.num_outputis set to 47.The error message is thrown here: https://github.com/apache/incubator-mxnet/blob/master/src/operator/slice_channel-inl.h#L208
num_outputsseems to be set here: https://github.com/apache/incubator-mxnet/blob/master/python/mxnet/module/base_module.py#L385 ... although this happens after self.forward is called, but the error message seems to be thrown beforenum_outputsis setAll reactions