Thank you Alex. It sounds like the MultiEncoder is not something that
is used at the OPF level, but that the OPF uses internally when
abstracting away the Network API complexity.

---------
Matt Taylor
OS Community Flag-Bearer
Numenta


On Thu, Sep 17, 2015 at 10:14 AM, Alex Lavin <[email protected]> wrote:
> Hi all,
> The MultiEncoder is useful in the Network API when there are multiple fields
> to encode. A common use case would be a CSV file with both a timestamp
> column and a scalar value column. This CSV is specified as the
> FileRecordStream [1] DataSource in the network’s sensor region (e.g. in
> Record Sensor [2]). The sensor region needs to know how to encode the data,
> so when creating the region we can specify both a DateEncoder and a
> ScalarEncoder via the MultiEncoder. There are several examples, including
> here in the hierarchy network demo: [3]. Hope this helps!
>
> [1]
> https://github.com/numenta/nupic/blob/master/nupic/data/file_record_stream.py
> [2]
> https://github.com/numenta/nupic/blob/master/nupic/regions/RecordSensor.py#L47
> [3]
> https://github.com/numenta/nupic/blob/master/examples/network/hierarchy_network_demo.py#L114-128
>
> Cheers,
> Alex

Reply via email to