-
Notifications
You must be signed in to change notification settings - Fork 70
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
LSTM example fails #197
Comments
Same problem here! |
Could you try to change in |
Thank you for your reply Pluskid. I tried the changes you recommended and got the following error:
On another note, there is a depreciation warning:
I haven't yet found where it's occurring but I will look into it. |
Last one is irrelevant, offending lines: you may just remove square brackets, and deprecation warning will be removed. |
Well, it looks like problem can be fixed by changing I can make a PR with fixes, but this solution looks somewhat inconvenient. I think it's better to change appropriately P.S.: there is also bug in |
Thanks Arkoniak, That definitely got me further than before Now I'm getting another error:
EDIT: It looks like I might have introduced a typo somewhere because I reinstalled MXNet and the char-LSTM example appears to be working fine now. Thank you! Now I can get back to figuring out the original problem of modifying the example to do things like translation. |
@Arkoniak The ambiguity comes from the fact when every arguments are passed via keyword argument, then the function signature is empty, and the method dispatcher does not know which one (symbolic or NDArray) to call. @TravisA9 It seems to be due to some encoding / decoding error reading your text file. Are you using non-ASCII text for testing? Maybe you need to check Julia document on how to properly decode a text file if you are not using UTF-8 encoding? |
@pluskid Just as an idea. Would it be wrong, to test arguments of function and if all of them is
It feels somewhat hacky, but it could work, I presume. |
@Arkoniak Yes, I agree this could be an option. We will need to define such wrapper for all the operators. |
Thank you @pluskid, you might well be right:
However, I suspect there may be more to this. As I mentioned above I downloaded MXNet again and reinstalled and it worked fine. This lead me to believe that I have somehow mistakenly introduced an error somewhere. But I have run the example with no changes a few times and though it works most of the time there are times that it suddenly spits out that error again. In those cases I have deleted the generated files(vocab.dat and input.txt) and it runs fine again. Not a big deal though! There is a second issue I have run into. In keeping with the mentioned scenario I decided to make a text (*txt) file with English->Nahuátl text ( just as a starting point ), swapping out input.txt for my language.txt file. I expected it to work because it is in fact UTF-8 text which I verified with different applications. Nahuátl text does have accent marks but somehow I don't think that is the problem I can't seem to find any important differences between this text and the original input.txt and nothing else has been changed from the char-lstm example. Once again the error is: EDIT: I tried running running char-lstm with language.txt after removing all accents and it still throws the error. |
@TravisA9 can you open a second issue with the encoding issue and post a small example, the error log, and if possible a reduced example? |
Ok, @vchuravy that's not a bad idea. I'll do that. |
I have the same problem when trying to execute the regression example Even following @Arkoniak suggestion to add
Any help is appreciated. |
Can you give gist of your code? Since there is no This line https://github.com/dmlc/MXNet.jl/blob/master/examples/regression-example.jl#L33 should be changed to either
or
Secondly https://github.com/dmlc/MXNet.jl/blob/master/examples/regression-example.jl#L40 should be altered to
with these changes code works fine. I'll send PR in near time. |
Right on! I was running the tutorial side-by-side with another dataset and they both got the same error. I just pasted the error from my run, rather than the tutorial. Nevertheless, your suggestion solves it. I also realized that the "mx.SymbolicNode" addition is only needed for the first layer. Thank you very much! |
I still have the issue with the LSTM example. Changing When I change it to 'FullyConnected(data=data, ....' I do get the change to the error saying it is Ambiguous, but when I use the proposed fix it doesn't help.
|
I did some test and realized that this is an issue that is seen on the latest release. @aaronc8 Maybe you can try @vchuravy Maybe we should consider making another bugfix release? |
Thanks for the reply - doing checkout seems to have fixed the original error, but now I'm getting
So in line 39-41 in an attempt to compile using
and then it gives me
where the whole text data is included in the error and at the end of the error it says
which I think meant that I am not doing Sorry, I'm not the most code savvy :( If it's any help - I do have an nvidia card but if it's simpler I'd rather just avoid incorporating CUDA and just use the CPU to just get the example to work. |
The "FullyConnected" do not work.
the error line of code:
https://github.com/dmlc/MXNet.jl/blob/master/src/symbolic-node.jl#L654
If I comment it, it will construct the symbolic graph, but can not execute it.
I am using the master branch with updated submodules.
The text was updated successfully, but these errors were encountered: