-
Notifications
You must be signed in to change notification settings - Fork 736
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
canonical estimator results in shape error #161
Comments
I am trying to run the twit example on other estimators. In this case canonical rnn.
I receive shape error.
my context length is 10. It seems as the ndarray has been squeezed somewhere. Full error:
|
@cyrusmvahid thanks for submitting this -- could you enclose snippets and error traces in triple ticks (`) to have it formatted nicely?
|
done |
Thank you, but remember to put triple ticks (```) one line before and one line after snippets and error traces. Sorry for being so pedantic, but nicely formatted issues are more likely to be looked into. |
sure
…On Mon, Jul 1, 2019 at 1:47 PM Lorenzo Stella ***@***.***> wrote:
done
sorry
Thank you, but remember to put *triple* ticks (```) one line before and
one line after snippets and error traces. Sorry for being so pedantic, but
nicely formatted issues are more likely to be looked into.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#161>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABLOVGKEB7UEZ5UDHGYVEXDP5HVFDANCNFSM4H4ROYDA>
.
|
Fixed in #254, closing |
Description
I am trying to run the twit example on other estimators. In this case canonical rnn.
Here is the code:
I receive shape error.
my context length is 10. It seems as the ndarray has been squeezed somewhere.
To Reproduce
Error Message
I am trying to run the twit example on other estimators. In this case canonical rnn.
Here is the code:
I receive shape error.
my context length is 10. It seems as the ndarray has been squeezed somewhere.
Environment
(Add as much information about your environment as possible, e.g. dependencies versions.)
The text was updated successfully, but these errors were encountered: