-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix derivative preserving fields from wrong point in stream #1414
Conversation
@phemmer Thanks! I'll take a look at this tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@desa Can you review this as well?
In summary the issue was we carried forward the other fields from the previous point instead of the current point, which is odd since the time is of the current point as well as the derivative result.
Makes sense why we didn't catch it first as it is not the most common use case but glad we now have tests for it ❤️.
@phemmer We are planning to release a version 1.3.1 with this fix. Can you change the PR to target the |
branch changed. |
LGTM 👍 |
@phemmer can you rebase onto |
Whoops. Didn't notice that after I switched the branch. Done. |
Yes please, I added a 1.3.1 section. |
done |
fix derivative preserving fields from wrong point in stream
#1333 changed the derivative node to add the derivative to the current point instead of the previous one. However due to a typo in the code, for stream nodes, it effectively resulted the emitted point containing the values of the previous point, the timestamp of the current point, and the derivative of the current point.
When using batch, the result was as it's supposed to be (values, timestamp, and derivative all from the current point). The batch code had the same typo, it worked because of ordering of the code.
Unfortunately there were no tests that would have caught the behavior, so I added some.
Required for all non-trivial PRs