I think this project is very useful and I've noted other projects in Go use it as well. Merely a suggestion, but I think you could make things simpler for people pulling this in if you have a tagged release tag to pull from. (See https://dave.cheney.net/2016/06/24/gophers-please-tag-your-releases) It is super quick to add in Github.

Thanks for writing this.

My main contribution is a benchmark to quantify the proposed performance enhancements by @nemothekid

Before:
< go test -run none -bench . -benchtime 2s
PASS
BenchmarkNumericHistogram20-8    3000000               891 ns/op
BenchmarkNumericHistogram50-8    2000000              1396 ns/op
BenchmarkNumericHistogram100-8   1000000              2120 ns/op
ok      github.com/signalfx/gohistogram 9.901s

After:
< go test -run none -bench . -benchtime 2s
PASS
BenchmarkNumericHistogram20-8   20000000               205 ns/op
BenchmarkNumericHistogram50-8   10000000               340 ns/op
BenchmarkNumericHistogram100-8   5000000               482 ns/op
ok      github.com/signalfx/gohistogram 10.964s

hello, I find the following a bit odd. I'll go take a look at the Java code, but either its wrong or can be simplified.

func ewma(existingVal float64, newVal float64, alpha float64) (result float64) {
    result = newVal*(1-alpha) + existingVal*alpha  // *** existingVal is always 0 ??
    return
}

func (h *WeightedHistogram) scaleDown(except int) {
    for i := range h.bins {
        if i != except {
            h.bins[i].count = ewma(h.bins[i].count, 0, h.alpha) //****  <--- 0 ??
        }
    }
}

You display in the README a printed histogram, but I can't find any instructions in the API docs for outputting the histogram to console. Is there an easy way to do this from your package?

When I'm using numeric histograms in different goroutines getting panic from time to time: runtime error: index out of range

Panic is here: github.com/VividCortex/gohistogram/numerichistogram.go:124

Welcome to WhiteSource for GitHub.com! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.

:vertical_traffic_light: WhiteSource for GitHub.com will start scanning your repository only once you merge this Pull Request. To disable WhiteSource for GitHub.com, simply close this Pull Request.

What to Expect

This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource for GitHub.com will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource for GitHub.com will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.

If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.

If WhiteSource Remediate Workflow Rules are set on your repository (from the WhiteSource 'Integrate' tab), WhiteSource will also generate a fix Pull Request for relevant vulnerabilities.

:question: Got questions? Check out WhiteSource for GitHub.com docs. If you need any further assistance then you can also request help here.

Outliers significantly affect the current merging algorithm. We can end up with situations like this:

Total: 109
-1000    .
-900     .
-800     .
-700     .
-600     .
-0.041725873527114175    .......................................
700      .
800      .
900      .
1000     .

Not a math person here, been looking into the code but no clue. I assume it must be pretty simple, so please bear with me.

How to get a count number for a specific bin value (numerichistogram)? Thank you 🙏🏻