vectormath alternatives and similar packages
Based on the "Science and Data Analysis" category.
Alternatively, view vectormath alternatives based on common mentions on social networks and blogs.

gonum
Gonum is a set of numeric libraries for the Go programming language. It contains libraries for matrices, statistics, optimization, and more 
Stats
A well tested and comprehensive Golang statistics library package with no dependencies. 
gosl
Linear algebra, eigenvalues, FFT, Bessel, elliptic, orthogonal polys, geometry, NURBS, numerical quadrature, 3D transfinite interpolation, random numbers, Mersenne twister, probability distributions, optimisation, differential equations. 
dataframego
DataFrames for Go: For statistics, machinelearning, and data manipulation/exploration 
gonum/mat64
The general purpose package for matrix computation. Package mat64 provides basic linear algebra operations for float64 matrices. 
calendarheatmap
📅 Calendar heatmap inspired by GitHub contribution activity 
TextRank
:wink: :cyclone: :strawberry: TextRank implementation in Golang with extendable features (summarization, phrase extraction) and multithreading (goroutine). 
sparse
Sparse matrix formats for linear algebra supporting scientific and machine learning applications 
evaler
Implements a simple floating point arithmetic expression evaluator in Go (golang). 
triangolatte
2D triangulation library. Allows translating lines and polygons (both based on points) to the language of GPUs. 
piecewiselinear
tiny linear interpolation library for go (factored out from https://github.com/sgreben/yeetgif) 
PiHex
PiHex Library, written in Go, generates a hexadecimal number sequence in the number Pi in the range from 0 to 10,000,000. 
GoStats
GoStats is a go library for math statistics mostly used in ML domains, it covers most of the statistical measures functions. 
godesim
ODE system solver made simple. For IVPs (initial value problems). 
assocentity
Package assocentity returns the mean distance from tokens to an entity and its synonyms 
bradleyterry
Package to do BradleyTerry Model pairwise compairsons 
gograph
A golang generic graph library that provides mathematical graphtheory and algorithms. 
mudlarkgo
A collection of packages providing (hopefully) useful code for use in software using Google's Go programming language.
Static code analysis for 29 languages.
Do you think we are missing an alternative of vectormath or a related project?
README
Vectormath for Go
This is an adaptation of the scalar C functions from Sony's Vector Math library, as found in the Bullet2.79 source code. (Note that the current svn for Bullet retains a subset of this library in a different location.) The full library can be found in the following directory of the Bullet2.79 source tarball:
Extras/vectormathlibrary/include/vectormath/scalar/c
Special thanks to Sony Computer Entertainment Inc. for allowing the use of their Vector Math library under a BSDstyle license, which made this possible.
Approach
Start with a direct conversion of the Sony library to Go. (This was shipping code, so we will assume it's correct.) Then iterate to make it more Golike, while trying to balance the twin goals of same/better performance and maintaining readability.
The C version of the library, as opposed to the C++ version, was chosen as a starting point mainly to avoid the distraction of function renaming, as the C++ version of Sony's library relies somewhat on operator and function overloads, which have no direct equivalent in Go.
Note that the original C library provides two versions of each file, e.g., vec_aos.h and vec_aos_v.h. I've brought over the former as opposed to the latter, since this simplifies things for beginners. The 'result' argument is always a pointer passed as the first argument to a function. Currently, the only types used in this library that are passed by value are simple types, e.g., float and int. Everything else is a pointer. (This should, in theory, simplify memory thrash considerations as well. In practice.. I have no idea. :)
Future Direction
Further research is required for determining:
 What makes the most sense for optimizing this code for SIMD
 Whether we should be passing vectors, etc., by value instead of reference
 If we should continue to declare vectors as individual values as opposed to an array of values. This would avoid the branching currently required to access members by index, but would disallow accessing members by common name (x, y, z and w) due to Golang's lack of a union equivalent.
 Whether it makes sense to stay with 32bit, or if we would get the same performance with 64bit
Feedback on this library is welcome and appreciated, though I make no promises about my ability to deliver on anything beyond what you see here. :)
License
I have licensed my modifications under a license similar to that of the original library on which this is based. See the LICENSE file for more details.
*Note that all licence references and agreements mentioned in the vectormath README section above
are relevant to that project's source code only.