Just don't use otypes, itypes. Implement the make_node() method. It isn't hard. We won't extend shortly as_op or otypes/itypes.
If you have question about make_node(), you can ask them. Fred On Tue, Aug 1, 2017 at 12:33 PM 'Michael Osthege' via theano-users < [email protected]> wrote: > sorry to dig up this old thread, but I am also working with pymc3 and have >>> a related problem: >>> >> > I am trying to create custom Ops for integrating an ODE model. I can > already do it with as_op, but that can't be pickled leading to problems > with parallelization in pymc3. > > I followed the theano documentation to implement a custom Op, but I > noticed a problem with the otypes. The *Ops otypes is a list of dvector, > but the length of that list can change with the Op parameters*. But the > itypes/otypes are not instance-attributes but class attributes. So > theoretically I *can't have multiply custom Ops of the same type that > have different itypes/otypes*, right? > > Also, do you have any idea how I could circumvent this? > > cheers > > -- > > --- > You received this message because you are subscribed to the Google Groups > "theano-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "theano-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
