Added support for optimized color conversion (extension to imagen.colors...

...paces) + NChannelGeneratorSheet
Hmm well I think it's still better to say it to strees the modifications?
I mean, if you plan to use monochrome generators it still is better to use
a simple GeneratorSheet, if not for else, for a slight performance
improvement?

G



On Wed, Jul 16, 2014 at 6:55 PM, James A. Bednar <notifications@github.com>
wrote:

> In topo/base/generatorsheet.py:
>
> > @@ -120,3 +122,107 @@ def start(self):
> >
> >      def input_event(self,conn,data):
> >          raise NotImplementedError
> > +
> > +
> > +
> > +
> > +class NChannelGeneratorSheet(
> GeneratorSheet):
> > +    """
> > +    A GeneratorSheet that handles input patterns with multiple simultaneous channels.
> > +
> > +    Accepts either a single-channel or an NChannel input_generator.  If the
> > +    input_generator stores separate channel patterns, it
> > +    is used as-is; if other (single-channel) PatternGenerators are used, the Class behaves
> > +    like a normal GeneratorSheet.
>
> Is this still true? I thought we no longer needed to distinguish between
> two types of generator?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ioam/topographica/pull/572/files#r15015602>.
>