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

PR #11 - Issue 117 - analytics updated to handle maxed out sensors #10

Merged
merged 2 commits into from
Oct 12, 2020

Conversation

JSegrave-IBM
Copy link
Collaborator

See Call-for-Code/Prometeo-Pyrrha#117

This PR covers the analytics side of issue 117. The firmware side is still required for the issue to be fully resolved.

…l value rather than a PPM for sensor readings, TWAs and Gauge values affected. See issue 117 for details.
… exceeded their range. This change makes sure the analytics handle that signal value correctly and updates the test data to reflect what the sensors are expected to send. Also standardised the use of pandas .loc selectors.
Copy link
Member

@upkarlidder upkarlidder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @JSegrave-IBM

@narengan narengan merged commit c0e71ff into Pyrrha-Platform:master Oct 12, 2020
@JSegrave-IBM JSegrave-IBM deleted the issue_117 branch October 12, 2020 14:54
@JSegrave-IBM
Copy link
Collaborator Author

@lidderupk @narengan - thank you!

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

Successfully merging this pull request may close these issues.

3 participants