Subutai Ahmad

This doesn’t affect any of our existing sparse networks right?

Where are our conventions now? They used to be on the wiki.... I believe filenames_are_snake (except Regions) but not sure about modules. This is basically taken from Python conventions.

Occurred again in another pipeline: ``` tests/unit/py2/nupic/research/spatial_pooler_compatability_test.py:293: SpatialPoolerCompatabilityTest.testCompatability2 FAILED =================================== FAILURES =================================== ______________ SpatialPoolerCompatabilityTest.testCompatability2 _______________ self = def testCompatability2(self): params = { "inputDimensions": [12,7], "columnDimensions": [4,15], "potentialRadius": 22, "potentialPct": 0.3,...

I'm not sure "major change to the algorithm" is the appropriate phrase here 😄 It's a relatively small bug fix that should improve robustness to noise in some cases, though...

I think they should be handled in the same PR - to me the two are intricately tied together. The two things mentioned are related to the same underlying problem...

@cogmission Yes. I should've listened to @rhyolight in the first place 😄 .

It's a valid point, and one we discussed quite a bit. We chose the current method due to the very high dynamic, but known, range of some of the streams....

The labels represent individual ranges labeled by humans. NAB uses anomaly windows for scoring because the anomalies are temporal and can span a period of time. These windows are in...

Hmm, not sure I remember all the details. I like the idea of using explicit precision as many places as possible. I don't know why someone might want unspecified versions...

OK, though wouldn't it be strange for the unspecified type to be platform specific? I guess that's how C is anyway.