Skip to content
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

implement clientside signal processing #1

Open
bcliang opened this issue Jul 8, 2019 · 2 comments
Open

implement clientside signal processing #1

bcliang opened this issue Jul 8, 2019 · 2 comments

Comments

@bcliang
Copy link
Owner

bcliang commented Jul 8, 2019

Ideas

  • use session store for input buffer (vs. recalculating trace each time)
  • simple moving average (Math.mean)
  • kalman filtering (kalmanjs)
  • generate new trace (add/extend) for filtered data on plot
@bcliang
Copy link
Owner Author

bcliang commented Jul 27, 2019

some working code exists here https://github.com/bcliang/dash-clientside-demo/tree/add-clientside-filter-example

TODO: because traces can have non-matching length (filter enabled/disabled) need a way to output CSV with aligned time. ALTERNATIVELY, just draw each trace as a separate pair of (X,Y) columns

@bcliang
Copy link
Owner Author

bcliang commented Aug 1, 2019

Made changes -- each trace has separate (x,y) paired column in CSV.

TODO: Refactor to eliminate confusing input validation performed in ui.relayout() and signal.filterSignal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant