5 ms·

Hey Hackers, this is my first full-featured Golang package. I took a lot of care to ensure it was well tested and provided a lot of common functions that I felt

Hey Hackers, this is my first full-featured Golang package. I took a lot of care to ensure it was well tested and provided a lot of common functions that I felt were missing from the standard library. In addition it has a lot of other statistics functionality like regressions, outliers, correlation and more.

Mithaldu 11y ago
The coverage seems to be only line-based. I don't know if it's relevant for Go, but you might want to see how the coverage looks like for branch-based analysis (if Go has software for that). Otherwise, nice to see someone take quality serious. :)
- anonfunction 11y ago
  The coverage is based on the built in go tooling, which supports line or function based analysis. In addition it can start a webserver where you can browse coverage by file with color output. # Generate coverage data go test -coverprofile=coverage.out # View coverage by function go tool cover -func="coverage.out" # View coverage line by line go tool cover -html="coverage.out"
faitswulff 11y ago
This seems like a really cool project to hack on. I noticed you have no issues on the github repo, but where do you want to go with it next? Or what would you like more eyes on?
- howeman 11y ago
  I mentioned elsewhere in the thread, but if you're interested in help buliding statistical tools for go, Gonum is always looking for more hands. Look at what we have in github.com/gonum, and/or come introduce yourself at gonum-dev
- anonfunction 11y ago
  Thanks for your interest! I think the biggest thing to do is finalize the public API and release v1.0.0. I started with only functions but have since added types, so I'd like to figure out if I should support both or stick to one or the other. I have a feeling I could use an Interface to make stats work for both []float64 and []int but I'm not sure about that. Another thing I'd like to do is add more test suites, I know they are out there for more mature statistics packages in other languages that could be ported to Go. Speaking of mature packages, I think the Gnu GSL Statistics[1] could be a good roadmap for future functionality and API design decisions. 1. http://www.gnu.org/software/gsl/manual/html_node/Statistics.html#Statistics http://www.gnu.org/software/gsl/manual/html_node/Statistics....

Mithaldu 11y ago

The coverage seems to be only line-based. I don't know if it's relevant for Go, but you might want to see how the coverage looks like for branch-based analysis (if Go has software for that). Otherwise, nice to see someone take quality serious. :)

anonfunction 11y ago
The coverage is based on the built in go tooling, which supports line or function based analysis. In addition it can start a webserver where you can browse coverage by file with color output. # Generate coverage data go test -coverprofile=coverage.out # View coverage by function go tool cover -func="coverage.out" # View coverage line by line go tool cover -html="coverage.out"

faitswulff 11y ago

This seems like a really cool project to hack on. I noticed you have no issues on the github repo, but where do you want to go with it next? Or what would you like more eyes on?

howeman 11y ago
I mentioned elsewhere in the thread, but if you're interested in help buliding statistical tools for go, Gonum is always looking for more hands. Look at what we have in github.com/gonum, and/or come introduce yourself at gonum-dev
anonfunction 11y ago
Thanks for your interest! I think the biggest thing to do is finalize the public API and release v1.0.0. I started with only functions but have since added types, so I'd like to figure out if I should support both or stick to one or the other. I have a feeling I could use an Interface to make stats work for both []float64 and []int but I'm not sure about that. Another thing I'd like to do is add more test suites, I know they are out there for more mature statistics packages in other languages that could be ported to Go. Speaking of mature packages, I think the Gnu GSL Statistics[1] could be a good roadmap for future functionality and API design decisions. 1. http://www.gnu.org/software/gsl/manual/html_node/Statistics.html#Statistics http://www.gnu.org/software/gsl/manual/html_node/Statistics....