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

Unwanted spurious spikes #41

Closed
Quaxo76 opened this issue Jan 17, 2018 · 2 comments
Closed

Unwanted spurious spikes #41

Quaxo76 opened this issue Jan 17, 2018 · 2 comments

Comments

@Quaxo76
Copy link

Quaxo76 commented Jan 17, 2018

My server has been behaving well, with no drops and no spikes. But the client, which has two sensors attached, sometimes shows large spikes, which are annoying especially because they mess up the autoscale of the y axis, and so I loose detail.
What is weird is that both sensors show the same spike, and it appears to be on only one frame. Could this be a communication error? It's hard to believe that both sensors always show the same spike at exactly the same moment...
temperature

temperature2

@Quaxo76
Copy link
Author

Quaxo76 commented Jan 18, 2018

Just realized this is a duplicate of #9 . I tried to apply the proposed solution by modifying my startup command to
su pi -c 'cd /home/pi/code/temperature-machine && ./start-client.sh -Davoid.spikes=30 &'
and rebooted. I'll see if it helps...

Cristian

@tobyweston
Copy link
Owner

tobyweston commented Jan 18, 2018

Great, make sure you get the latest version for that feature. When it's on, the log will show when it detected a spike and through the value away. Let me know if you see any.

This has been a huge pain for me as its hard to reproduce and I get it all the time across machines. I really have no idea at this point as the smoothing feature doesn't work for me (although its tested so works "in theory"). I've started to suspect electrical interference!

The new download CSV feature is partly there to help me figure out why the spikes aren't getting smoothed. Perhaps you could grab some images and CSV and attach to #9 and we'll see if it helps diagnose?

Closing this issue.

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

2 participants