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

...paces) + NChannelGeneratorSheet
Sounds good!



On Wed, Jul 16, 2014 at 7:14 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.
>
> Sure, we can include text that compares GeneratorSheet and
> ChannelsGeneratorSheet, saying when you might want to use one, and when you
> might want to use the other. But that should be separate from the
> description of what ChannelsGeneratorSheet does. I.e., here we should be
> saying that we take any PatternGenerator, that we use the channels() method
> to obtain any channels of data provided by it, and that we make those
> available on various output ports. We can say this clearly, simply, and
> without any reference to what other classes do. Then we can add helpful
> information saying that people who know they only want a single output
> should not use this class, and should use GeneratorSheet instead.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ioam/topographica/pull/572/files#r15016856>.
>