* initial implementation of multidimensional std and var
* consolidated std function into var, cleaned up the interface for var, fixed bias correction
* added documentation of variable axis for std and var
* updated documentation for std and var
* changed the order of normalization and dimension for a three parameter input in the functions
* updated documentation for var and std
* add transform expressions for std and var with variable axis
* added test coverage for std and var with a variable axis
* update to documentation
* change n dim std to use apply function
* fixed tests, removed unnecessary code, updated docs
* fixed typo in docs
* update docs to remove a type
* changed location of apply function
* updated tests to use deepStrictEqual to pass linter
* adding test coverage for var.transform and std.transform
* add placeholder for apply function
* added apply function
* add test coverage for apply utility
* stylsitic name change in apply source code
* stylistic format change to test
* improved description of function parameters
* moved the apply function to the public matrix functions
* update location and reference of unit test
* fixed function reference paths in apply for location in function
* changed path to apply in apply.test
* make apply a typed function, update unit test
* added typing error test to coverage
* remove apply.test.js from the utils test function
* added transform function for apply
* add unit test for apply.transform.js
* Minimally working
* Added tests, toString
* Added tests for evaluation
* Minor changes
* Added a line in the docs about chained conditionals
* Documentation, replacing var and let with const
* chore(package): update standard to version 12.0.0
* update to new lint version with --fix
I believe this mainly adds whitespace to `{}`'s.
* Replace assert.equal with assert.strictEqual
This breaks a lot of tests which I will endevour to fix in the next
commits.
* Fix most errors due to assert.strictEquals
Some instances of `strictEquals` are replaced by `deepEquals`.
`toString` has been used to make some string comparisions explicit.
Tests will still fail untill #1236 and #1237 are fixed.
* Fix assertion erros due to -0
With node 10, assert.strictEqual no longer considers `0 === -0`.
I missed these first time round as I was using node 8.
* Put toString correct side of bracket
I was converting the constructor to a string rather
than the result of the computation. Oops.
* Fixed#1236: quantileSeq has inconsistant return
* Update package-lock
* Fixed#1237: norm sometimes returning a complex number instead of number
* Fix cli tests
* More changes for standardjs, and fixes in unit tests
