You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is mildly related to #44. I was writing some of my own tests my use of TimeSeries when I noticed that I was missing some events when using atTime and bisect. Here's an example:
v0.7.1
- renaming columns now does so with mapKeys, rather than breaking the whole thing apart
- fixes merging of TimeSeries so that if the result isn't chronological then it will sort them before trying to make a new TimeSeries
- fixes atTime() boundary condition (#45)
- fixed align processors to handle initial events that are already aligned
- internal calls to setCollection can skip the isChronological test with a flag since they know they are maintaining order.
This is mildly related to #44. I was writing some of my own tests my use of
TimeSeries
when I noticed that I was missing some events when usingatTime
andbisect
. Here's an example:I think this is because at https://github.com/esnet/pond/blob/master/src/pond/lib/collection.js#L192, instead of
if (pos && ....)
you actually wantif (pos >= 0 && ...
).The text was updated successfully, but these errors were encountered: