For now only strings are accepted as the measures parameter in GridSearchCV, RandomizedSearchCV, and cross_validate. It's thus impossible to use those with measures that take specific parameters as input (e.g. #156 ), or to use custom measures.

We should then accept callables in addition to strings.

Each callable should only take the predictions parameter. In order to handle measur

See:
gonum/gonum#845 (comment)

Using multiple [[gateway]]

The help currently reads:
Vector S get; set;
Gets the singular values (Σ) of matrix in ascending value.

It should be:
descending order of magnitude.

Hi everyone,

I am building a sensor fusion framework based on nalgebra, and found out that we do not have support for Lie algebra operations like expmap and logmap. Is is appropriate to add them here or should I implement them in my own crate by using some traits?

Many thanks,

Fan

I am submitting a Feature Request

Lack of description of the "-l" lock option in the man page.
The option is proposed when you type "cmatrix -h" to get help text, but anything in man page.

Request :
Complete the man page (and add the manner to quit this lock screen.)
Or suppress this option that force you to reboot if you don't know how to "unlock"

Tested on GNU/Linux Debian 10 Buster

In several places for postgres, we CREATE SEQUENCE .... We do this for every table which uses the sequence, partly for clarity and partly so we don't assume someone else has done it for us.

Instead, we should put these database-level SQL queries in a dedicated section, rather than in each _table.go.

In the documentation, the sentence A trait representing an affine transformation that can be applied to points or vectors. An affine transformation is one which is cut off. I'm not sure how it's meant to end and don't know enough about what an affine transformation is to fix it, but thought I'd point it out 😄

Docs about dest param :
"You can pass all parameter same (this is similar to m1 *= m1), you can pass dest as m1 or m2 (this is similar to m1 *= m2)" (c)

But some functions behave differently. For example:

vec3 A = {0,0,2};
vec3 B = {2,0,0};
glm_vec3_cross(A, B, A); // A = {0, 4, -8} was expected A = {0, 4, 0}

• Proposal

Using DocFX, it’s possible to automatically get a documentation website that is in synced with the source implementation. A good use case for this proposal is to quickly check the differences between the math library here and the one located in opentk.

Alternatives

None at the time.

When installing on OSX Catalina, the system prevents installation by double clicking and the basic right click open doesn't work either.

The correct way to install is to open system preferences > Security & Privacy and click the allow button on the screen.

Current normalization code is as follows:

    public Vector3d normalize(Vector3d dest) {
        double invLength = 1.0 / length();
        dest.x = x * invLength;
        dest.y = y * invLength;
        dest.z = z * invLength;
        return dest;
    }

Instead division by zero should always be avoided, and the code should be something like the following to prevent divis

Quaternion sends (-1,-1) for image dimensions when requesting an author avatar. This is because the respective QML defines width and height but not sourceSize - which is, obviously, a shortcoming.