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

Discard outliers in data, ex. response time of Null, 0, or very large number #32

Open
kmcurry opened this issue Oct 10, 2017 · 4 comments

Comments

@kmcurry
Copy link
Owner

kmcurry commented Oct 10, 2017

At national Day of civic hacking 2017 a city of Virginia Beach is data scientist told me that average response time is a bad indicator due to situational factors. For example, in an emergency situation and officer might have to choose between logging the arrival time and responding.

@jamjohns
Copy link
Collaborator

I'm assuming he meant the trimmed mean, or some form of standard deviation. Can you describe the formula used vs. what was proposed?

@kmcurry
Copy link
Owner Author

kmcurry commented Nov 16, 2017

I'm just summing the values and dividing by number of values. Natasha Singh-Miller suggested a different method but I don't know what. We can ask her. We should filter outliers for sure.

@kmcurry
Copy link
Owner Author

kmcurry commented Nov 16, 2017

I've just realized I've been using the wrong terms here. Current method is sum of values divided by number of values (average, mean). We need a better method that discards outliers such as extremely long response times and possibly instantaneous (0) response times.

@jamjohns
Copy link
Collaborator

Yeah that's what I thought you meant. I wasn't sure if you had a specific method in mind, or just something better than average.

@kmcurry kmcurry changed the title Change average response time to mean Discard outliers in data, ex. response time of Null, 0, or very large number Sep 24, 2018
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