It is almost impossible to learn how to use SparseMatrix from the current documentation. The example code also isn't very useful. We need to improve the documentation and make it easier to grasp and include some real-world examples.

(Possibly related to #1166 and #1770?)

currently, it is unclear how to go back and forth between flash graph objects, sparse flash matrices, dense flash matrices, and R matrices. it would be good to be more clear about how this works. For example, I can convert my flashgraph to a sparse graph with fg.get.sparse.matrix(graph), but there is no way to retrieve a dense matrix from that, and consequently, I cannot use as.matrix() to convert

Take the text Please login before uploading. and make it clickable so that it opens the Login form, and then updates the File Browser post-authentication.

Rawgit seems to be shutting down, as can be seen when you click the "source" button in the documentation. Maybe we could move it under unicredit.github.io/neo/?

This might be related to nim-lang/Nim#5199

Setup: Nim v0.16, linalg 0.6.6 on OSX

import linalg

## Training
let data = matrix([
                [1.2, 0.7],
                [-0.3, -0.5],
                [3.0, 0.1],
                [-0.1, -1.0],
                [-1.0, 1.1],
                [2.1, -3]
                ])
#echo data

Without `ech

The changelog is currently maintained here: https://hackmd.io/58CqcVmnRoGq-X5gIrNThg

My suggestion is to move it to a new wiki page: https://github.com/aardvark-platform/aardvark.docs/wiki
And link it in the ReadMe of aardvark.base: https://github.com/aardvark-platform/aardvark.base

As the ReadMe is actually a general Aardvark overview I'm not sure how to exactly integrate this.
Likewise,

To start with, it should handle 1-dimensional functions of these types:

• Polynomials (ax + b)
• Exponentials (a * b^x)
• Logarithmic (b log a)

Should be able to:

• Provide the derivative function
• Provide the integral function

In Numeric.Matrix: perspective and orthogonal currently follow OpenGL conventions. They require negative near and far values, otherwise they produce bogus Z values and messed up signs. The haddock comment on perspective states "Near plane clipping distance (always positive)" which is wrong. I suppose the OpenGL convention sees them as z-coordinates of the planes in screen space instead o