RiverView traffic tutorial problem

After changing, I am able to start nodejs web client and able to access to http://localhost:8083 as per tutorial. However, I still can’t see any data in the web interface just like the video tutorial u created.

i checked in mysql, data is there but there’s no anomaly score generated.

mysql> select * from metric_data limit 5;
+----------------------------------+-------+---------------------+--------------+-------------------+---------------+---------------+-----------------------------+
| uid                              | rowid | timestamp           | metric_value | raw_anomaly_score | anomaly_score | display_value | multi_step_best_predictions |
+----------------------------------+-------+---------------------+--------------+-------------------+---------------+---------------+-----------------------------+
| 01a07d7cf2e746688c2970413e35aa0b |     1 | 2016-01-08 13:54:07 |        11.18 |              NULL |          NULL |          NULL | NULL                        |
| 01a07d7cf2e746688c2970413e35aa0b |     2 | 2016-01-08 14:23:07 |         9.94 |              NULL |          NULL |          NULL | NULL                        |
| 01a07d7cf2e746688c2970413e35aa0b |     3 | 2016-01-08 14:38:07 |          8.7 |              NULL |          NULL |          NULL | NULL                        |
| 01a07d7cf2e746688c2970413e35aa0b |     4 | 2016-01-09 23:27:13 |        57.79 |              NULL |          NULL |          NULL | NULL                        |
| 01a07d7cf2e746688c2970413e35aa0b |     5 | 2016-01-13 13:42:48 |        11.81 |              NULL |          NULL |          NULL | NULL                        |
+----------------------------------+-------+---------------------+--------------+-------------------+---------------+---------------+-----------------------------+
5 rows in set (0.00 sec)

Here’s anomaly service log:

sport.py", line 48, in connect
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused
2017-01-10 06:19:31,388 - htmengine.anomaly(4073) - INFO - VER=0.0.0, SERVICE=ANOMALY  {TAG:ANOM.START} argv=['/home/meharu/numenta-apps/htmengine/htmengine/runtime/anomaly_service.py']
2017-01-10 06:19:31,397 - nta.utils.amqp.synchronous_amqp_client(4073) - INFO - Created consumer=Consumer(tag='channel-1-1', queue='traffic.mswapper.results'); queue='traffic.mswapper.results', noLocal=False, noAck=False, exclusive=False
2017-01-10 06:37:14,347 - htmengine.anomaly(9142) - INFO - VER=0.0.0, SERVICE=ANOMALY  {TAG:ANOM.START} argv=['/home/meharu/numenta-apps/htmengine/htmengine/runtime/anomaly_service.py']
2017-01-10 06:37:14,357 - nta.utils.amqp.synchronous_amqp_client(9142) - INFO - Created consumer=Consumer(tag='channel-1-1', queue='traffic.mswapper.results'); queue='traffic.mswapper.results', noLocal=False, noAck=False, exclusive=False
1 Like

Is there any error in the node.js console?

I’m afraid that there are problems with River View, the data service providing the JSON for this experiment. The NYC traffic data I see there is over 9 months old: http://data.numenta.org/nyc-traffic/199/data.html

I think I’m going to need to figure out what’s wrong with the data service.

Likely related: River View problems

There was an error during the data is pushing from client sth like “JavaScript heap out of memory” after like 30 minutes, but I tried to run again with command “node --max_old_space_size=4096 index.js” it run till the end. but just there’s some problems mentioned above.

@vannroath.ky Unfortunately, I don’t think I can work on this issue right away. Seems like there is a problem with the example that needs a longer investigation. I will prioritize this work and let you know when I have found the problem.

ok, noted. hope you can manage time and settle this problem.

Hi @rhyolight
Is there any update/fix toward this problems so far?

Unfortunately, no. I have plans on working on River View next month.

Hi @rhyolight
I hope you now have some spare time checking on this. And sorry if i’m urging or disturbing you too much.