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

Prefer doing integral math in data processing routines #79

Open
rbuch opened this issue May 16, 2019 · 0 comments
Open

Prefer doing integral math in data processing routines #79

rbuch opened this issue May 16, 2019 · 0 comments
Assignees

Comments

@rbuch
Copy link
Contributor

rbuch commented May 16, 2019

There are various places in the codebase where numbers/calculations are in floating point when dealing with discrete data (for example, Communication Over Time, in which the data arrays are kept as rates (msgs/second, for example), but have to be converted back to number of messages, an integral value, at some points). This can cause slight errors due to rounding and increases memory usage and computational load.

One cleanish way to fix this is to allow the graphing classes to accept integral data with some sort of option to also pass in a time interval (in the case of time series data), which can then be toggled on or off to display the rate of the data (msgs/sec) or the raw data (# msgs in interval). This would allow the underlying data arrays to be some kind of integral array type while still providing rate-based graphs.

@rbuch rbuch self-assigned this May 16, 2019
@rbuch rbuch changed the title Prefer doing integer math in data processing routines Prefer doing integral math in data processing routines May 16, 2019
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