New Object Early Community Build #3 and 4-5-6: FluidDataSeries, and DTW-based classification and regression - NOW IN SC TOO

Development and Maintenance
12

ok people, I think i will start a new thread to merge this and this other one: FluidDataSeries....in SC

@mccrmck has found a bug in the printing, I fixed it.

more importantly, he found what I find 2 confusing interface decisions I want to propose fixes to:

  1. getFrame should really be called getPoint to stick to DataSet - a frame is only a point in time so no need for a new concept… or do we? Frames are Points at a give Time?

  2. the printing (and json dump) prepend a T to the frame number to stress that it is a Point in Time - but when we query, we query only with the numerical value of it. For instance, 2 and not T0002. maybe we should either
    2.1 print without T
    2.2 query with the trimmings

Any feedback welcome. I know very few of you have tried this but you might still have strong opinions :slight_smile:

1 Like