scan module imports sandbox.cuda - hilarities ensue on badly configured OS X about theano HOT 11 CLOSED

Is this in theano stable as well?

from theano.

Yes I think so. This was introduced long long time ago. I've tried at one
point to fix it (before we moved to git) but it turned out not to be a
trivial task. I'll give it another go,
but know that this will not be done in a matter of minutes :(. Maybe I can
disable scan working on GPU for now removing the import (that should be
quick) and work on
repairing the damage afterwards.

Razvan

On Thu, Oct 20, 2011 at 8:53 PM, David Warde-Farley <
[email protected]>wrote:

Is this in theano stable as well?

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

I've looked through the code. cuda is imported only inside two functions
(exactly where I need it) when you use scan. So is it that the code that
generates the error actually uses scan, or this error happens even if you do
not use scan?

Razvan

On Fri, Oct 21, 2011 at 8:39 AM, Razvan Pascanu [email protected] wrote:

Yes I think so. This was introduced long long time ago. I've tried at one
point to fix it (before we moved to git) but it turned out not to be a
trivial task. I'll give it another go,
but know that this will not be done in a matter of minutes :(. Maybe I can
disable scan working on GPU for now removing the import (that should be
quick) and work on
repairing the damage afterwards.

Razvan

On Thu, Oct 20, 2011 at 8:53 PM, David Warde-Farley <
[email protected]>wrote:

Is this in theano stable as well?

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

This seems straightforward, no?

1. https://github.com/Theano/Theano/blob/master/theano/__init__.py#L80

2. https://github.com/Theano/Theano/blob/master/theano/scan_module/scan.py#L56

On Fri, Oct 21, 2011 at 10:35 AM, Razvan Pascanu
[email protected]
wrote:

I've looked through the code. cuda is imported only inside two functions
(exactly where I need it) when you use scan. So is it that the code that
generates the error actually uses scan, or this error happens even if you do
not use scan?

Razvan

On Fri, Oct 21, 2011 at 8:39 AM, Razvan Pascanu [email protected] wrote:

Yes I think so. This was introduced long long time ago. I've tried at one
point to fix it (before we moved to git) but it turned out not to be a
trivial task. I'll give it another go,
but know that this will not be done in a matter of minutes :(. Maybe I can
disable scan working on GPU for now removing the import (that should be
quick) and work on
repairing the damage afterwards.

Razvan

On Thu, Oct 20, 2011 at 8:53 PM, David Warde-Farley <
[email protected]>wrote:

Is this in theano stable as well?

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

Hmm .. sorry for that. I somehow missed that import ( I import cuda also in
scan_op and scan_utils, but there only inside the functions that need it).
I've moved the import cuda inside the scan function. Hopefully this will
make things better for those who don't use scna.

I'll work on removing it completely, but I do not have a lot of time to
dedicate to Theano
unfortunately...

Razvan

On Fri, Oct 21, 2011 at 10:40 AM, James Bergstra <
[email protected]>wrote:

This seems straightforward, no?

1. https://github.com/Theano/Theano/blob/master/theano/__init__.py#L80

https://github.com/Theano/Theano/blob/master/theano/scan_module/scan.py#L56

On Fri, Oct 21, 2011 at 10:35 AM, Razvan Pascanu
[email protected]
wrote:

I've looked through the code. cuda is imported only inside two functions
(exactly where I need it) when you use scan. So is it that the code that
generates the error actually uses scan, or this error happens even if you
do
not use scan?

Razvan

On Fri, Oct 21, 2011 at 8:39 AM, Razvan Pascanu [email protected]
wrote:

Yes I think so. This was introduced long long time ago. I've tried at
one
point to fix it (before we moved to git) but it turned out not to be a
trivial task. I'll give it another go,
but know that this will not be done in a matter of minutes :(. Maybe I
can
disable scan working on GPU for now removing the import (that should be
quick) and work on
repairing the damage afterwards.

Razvan

On Thu, Oct 20, 2011 at 8:53 PM, David Warde-Farley <
[email protected]>wrote:

Is this in theano stable as well?

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

Thanks Razvan, just moving it out of the global import path is a good
enough for now I think. Put a comment next to the internal import
documenting why it isn't a global import, and that'd be fine by me.

• James

On Fri, Oct 21, 2011 at 10:45 AM, Razvan Pascanu
[email protected]
wrote:

Hmm .. sorry for that. I somehow missed that import ( I import cuda also in
scan_op and scan_utils, but there only inside the functions that need it).
I've moved the import cuda inside the scan function. Hopefully this will
make things better for those who don't use scna.

I'll work on removing it completely, but I do not have a lot of time to
dedicate to Theano
unfortunately...

Razvan

On Fri, Oct 21, 2011 at 10:40 AM, James Bergstra <
[email protected]>wrote:

This seems straightforward, no?

1. https://github.com/Theano/Theano/blob/master/theano/__init__.py#L80

https://github.com/Theano/Theano/blob/master/theano/scan_module/scan.py#L56

On Fri, Oct 21, 2011 at 10:35 AM, Razvan Pascanu
[email protected]
wrote:

I've looked through the code. cuda is imported only inside two functions
(exactly where I need it) when you use scan. So is it that the code that
generates the error actually uses scan, or this error happens even if you
do
not use scan?

Razvan

On Fri, Oct 21, 2011 at 8:39 AM, Razvan Pascanu [email protected]
wrote:

Yes I think so. This was introduced long long time ago. I've tried at
one
point to fix it (before we moved to git) but it turned out not to be a
trivial task. I'll give it another go,
but know that this will not be done in a matter of minutes :(. Maybe I
can
disable scan working on GPU for now removing the import (that should be
quick) and work on
repairing the damage afterwards.

Razvan

On Thu, Oct 20, 2011 at 8:53 PM, David Warde-Farley <
[email protected]>wrote:

Is this in theano stable as well?

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

Just an idea to fix the problem, why not make gpu_hook in scan_module and have the import of cuda register fct in those hook?

Maybe there is better way to fix it, but this can work in all case I think and would solve the problem for people that use scan.

from theano.

Is this issue resolved by pull request #139? Can it be closed now?

from theano.

Just partially (as long as you do not use the scan op). So I think it
shouldn't be close just yet, because it can be solved in all cases with a
bit of care.

Razvan

On Mon, Oct 24, 2011 at 3:14 PM, David Warde-Farley <
[email protected]>wrote:

Is this issue resolved by pull request #139? Can it be closed now?

Reply to this email directly or view it on GitHub:
#134 (comment)

from theano.

Should we close it now?

from theano.

I think we can close it as now we should always be able to import cuda even if it isn't there. scan don't do it at import, so it is good I think.

from theano.