New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow predictions for multiple fields per model #1712

Open
scottpurdy opened this Issue Jan 4, 2015 · 8 comments

Comments

Projects
None yet
7 participants
@scottpurdy
Copy link
Contributor

scottpurdy commented Jan 4, 2015

It would be nice if you could specify multiple fields to make predictions for.

This will require a change to the CLAModel to support multiple classifier regions. It currently supports only one with the region name "Classifier":

n.addRegion("Classifier", "py.%s" % str(clRegionName), json.dumps(clParams))

Additionally, the OPF and description.py format will need to be updated to support multiple fields to predict. It require some changes to metrics or swarming so it knows which field (or fields?) to use for optimization.

There are two implementations of the classifier, so we will need a task in nupic.core for the C++ implementation.

@subutai

This comment has been minimized.

Copy link
Member

subutai commented Jan 5, 2015

OPF is setup in an OO way to support different model features. Is it possible to implement this feature as a subclass of CLAModel or perhaps as a separate independent model type? This would avoid disrupting or complicating the (already overly complex) clamodel.py. The factory would be used to instantiate the correct class type and after that everything else should just work.

@rhyolight

This comment has been minimized.

Copy link
Member

rhyolight commented Jan 8, 2015

@salexashenko You going to tackle this?

@salexashenko

This comment has been minimized.

Copy link
Contributor

salexashenko commented Jan 8, 2015

Yes

@rhyolight rhyolight modified the milestones: 0.3.0, 0.2.0 Jan 21, 2015

@rhyolight rhyolight removed this from the 0.3.0 milestone Feb 21, 2015

@rhyolight rhyolight removed the stand-alone label Feb 25, 2015

@JonnoFTW

This comment has been minimized.

Copy link
Contributor

JonnoFTW commented Oct 6, 2015

Any progress on this so far?

@rhyolight

This comment has been minimized.

Copy link
Member

rhyolight commented Oct 6, 2015

Nothing yet.

@yyccR

This comment has been minimized.

Copy link

yyccR commented Jan 6, 2017

So, any progress on this till now?

@rhyolight

This comment has been minimized.

Copy link
Member

rhyolight commented Jan 6, 2017

Nothin yet. To be clear, Numenta has not prioritized this task. If any work is going to get done here, it is going to be community-driven.

@dhirajrai1

This comment has been minimized.

Copy link

dhirajrai1 commented Mar 29, 2018

Hi any progress on predicting the multiple fields..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment