These are chat archives for libmir/public

22nd
May 2017
drug007
@drug007
May 22 2017 04:38
Hello! @9il is there a way to handle timeseries where there are several identical timestamps with different data assigned?
Ilya
@9il
May 22 2017 04:41
@drug007 Can you provide data example and describe how data should be handled?
drug007
@drug007
May 22 2017 07:20
sure. I have serveral timeseries from different sources that generate different data and process them simultaneously. But there is probability that timestamps in different timeseries will be equal - that is there will be several observations from different sources at the same time. As I understand now time in mir.timeseries.Series is unique and do not let handle two different observations with the same timestamp?
I can use my own type to represent timestamp - for example its low bits can be used to represent order no to distinct different observation with the same time and the rest bits to represent time itself.
Ilya
@9il
May 22 2017 11:02
@drug007 Yes, Series indexing algorithms assumes that timestamps are unique. BTW, Series allow to have multiple columns
Special timestamp type looks like a good idea
drug007
@drug007
May 22 2017 11:37
multiple columns is a good idea too, but how efficient it is? Probability of several observations with the same time is rather low and it will be sparse data structure - more than 90% and even more time will have corresponding data only in single column and the rest will be empty.
Ilya
@9il
May 22 2017 11:50
then your aproach is the best here
drug007
@drug007
May 22 2017 11:53
ok, I see. btw thank you for your good work!
dextorious
@dextorious
May 22 2017 19:05
Okay, so since the GitHub discussion seemed to indicate that my experience with learning Mir by porting some simple C++ code might have some value, I'll finish up my code and start writing a blog post towards the end of this week. Lots of silly questions incoming, no doubt. :)
On that note, one thing I noticed when I looked at the Mir blog is that even the more recent posts might need some revising. For instance, http://blog.mir.dlang.io/ndslice/algorithm/optimization/2016/12/12/writing-efficient-numerical-code.html makes extensive reference to mir.ndslice.algorithm.ndEach, which doesn't seem to exist any more. I'm not sure if that entire pattern is out of date or if it's just a few names that have changed in the API, but that's not an isolated case.