Basically, it only works to find optimal aggregation and model params for one scalar stream of data (with a timestamp). I believe @ycui wrote this code, so he might have more to say.
It’s a compatibility test to ensure that we get comparable results on NAB data when using the NAB’s params or the params generated by the param finder. I think it’s a useful test to port as well, if you are thinking of porting param_finder.py to HTM java.
You’re welcome. Thanks for pointing out the existence of that compatibility test. I believe that will come in handy if/when it becomes obvious that I’m going to port the param finder. For now my brain is NAB-fried… with butter on top! So I need a rest…