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
Fix/remove confusing __iter__ implementation in theano.tensor.var.TensorVariable #42
Comments
Hm, what does In any case, this is certainly not expected and an odd error. Unfortunately the pymc3 veneer on top of theano is thin so when something breaks you are left with theano's error messages which can be hard to read. |
|
Hi @Horatiu could you try converting that to int32 and see if that works? On Tue, Nov 1, 2016 at 1:28 PM, Horatiu notifications@github.com wrote:
Peadar Coyle |
Hi @springcoil, converted and same issue. |
Please consider the issue (very) low priority -- I have a working example, I just want to understand why passing the numpy array explicitly is required. |
Interestingly, it works if you pass it to |
Is this something that should go into the pymc-devs/pymc#1488 example? |
Closing as I am not able to reproduce this error (feel free to reopen is still a problem). @RogerTheAlien you may want to check this repository. |
Hi, I know I'm coming late here, but I see the same problem: in some cases, pymc3 fails to use pandas series, throwing a value error:
|
Thanks, probably a theano issue. @brandonwillard any idea? |
Totally unrelated, but I just have to give the pymc-team a whole bunch of cudos: Ive been using pymc2 for the past 4-5 years, unable to upgrade due to my very weird setup - windows + cygwin - but decided to bite the bullet and migrate to Linux... installing pymc3 worked like a charm, and BOY am I impressed by the way pymc has evolved, lots of new functionality and supporting features for analysis, plotting etc... Im very impressed!
—Tommy
+ sent from my iPhone
… On Aug 17, 2020, at 10:06, Thomas Wiecki ***@***.***> wrote:
Thanks, probably a theano issue. @brandonwillard any idea?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The problem appears to be the product |
@brandonwillard But it would work if |
I suppose we could consider adding that into our Theano fork, but only if it doesn't involve adding a new Pandas dependency. |
It should be easy to test whether |
Yeah, that's exactly what I was thinking. We could try adding this to the |
After some investigation, I've found that there is already support for the conversion of Pandas objects; however, the exact problem observed in this issue prevents use of the relevant logic. Specifically, the class If you look at the implementation of In other words, this design needs to be fixed. One simple approach is to create a The aforementioned fix has been split off into its own issue: #93. That's the correct first step toward fixing this particular issue. |
Duplicate of #93 |
I'm trying to translate Statistical Rethinking from R and RStan to Python and PyMC3.
On page 304, there's a simple logistic regression example. Data being used (publicly available):
Data is stored in a pandas DataFrame object. When I try and fit the model using:
I get the following error (which seems similar to pymc-devs/pymc#918):
The error is not very informative, and doesn't seem to point to my code.
But when using:
So explicitly passing in the numpy array rather than the pandas Series:
Everything works as expected. I'm just trying to figure out why that is? Is there a reference in the documentation for this behavior? What is the lesson I should take away from this? :)
Using pandas 0.19, numpy 1.11, pymc3.0rc2
The text was updated successfully, but these errors were encountered: