From the https://github.com/numenta/nupic.git repo:
nupic/datafiles/extra/hotgym/hotgym.csv -Conor -----Original Message----- From: nupic [mailto:[email protected]] On Behalf Of Matthew Taylor Sent: Wednesday, September 16, 2015 3:40 PM To: Kearney, Conor Subject: Re: sequence reset Conor, Exactly which hotgym example are you running? The tutorials I've put together don't use resets or sequences in the input CSV data. I think you found some lower-level examples of swarming. Please tell us exactly what CSV files in the codebase you are running as input data. Thanks, --------- Matt Taylor OS Community Flag-Bearer Numenta On Wed, Sep 16, 2015 at 7:35 AM, Kearney, Conor <[email protected]> wrote: > Hello, > > > > I am running the hotgym example and have a question about the sequence > reset mechanism. I note in the csv, the column 'gym' has an 'S' tag for > sequence. > When running the model, I check the value of sequenceReset from > sequenceReset = result.sensorInput.sequenceReset. > > > > This value is never 1, despite the gym name changing 5 times in the csv. > > > > Am I checking in the correct place for the sequenceReset flag? > > Does sequenceReset need to be explicitly stated somewhere in the json > for swarming or model_params for prediction? > > > > I assumed if the flag is marked as 'S' in the data csv then the reset > would be in effect for swarming and prediction. > > > > Thanks, > > Conor Kearney > > > > Conor Kearney > Data Scientist > Product Operations - QR&A > Allstate Northern Ireland > 9 Lanyon Place > Belfast > Phone: 847-326-8495 > Allstate Ext: 68495 > UK Phone: 02890678495 > Email: [email protected] > > > > The information contained in this message may be privileged and > confidential and protected from disclosure. > If the reader of this message is not the intended recipient, or an > employee or agent responsible for delivering this message to the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > > If you have received this communication in error, please notify us > immediately by replying to the message and deleting it from your computer. > >
