From the end of that post:

PS: the generated link to .cholesky() when using the search functionnality is wrong Oo. It should point to http://nalgebra.org/rustdoc/nalgebra/base/type.SquareMatrix.html#method.cholesky but points instead to http://nalgebra.org/rustdoc/nalgebra/linalg/cholesky/type.SquareMatrix.html#method.cholesky .

See dimforge/nalgebra#614.
This is out-of-date as the index parameter was modified by dimforge/nalgebra#490.

See dimforge/nalgebra#672:

The construction of LU, FullPivLU and QR for non-square matrices are all implemented. However their methods related to inverse/solve are only implemented for square matrices.

The current paragraph about the Unit type only explains how to use it, but not how to initialize it.

A dedicate about converting between various types from nalgebra would be very useful since the rustdoc-generated documentation is too dense to find out clearly what can be converted to what, and how.

See https://discourse.nphysics.org/t/nalgebra-ffi-guide/197/3?u=sebcrozet

See https://discourse.nphysics.org/t/documentation-about-calculations-and-arithmetics/387 for a detailed comment.

This page would list the kind of operations like the_matrix.column_iter_mut().for_each(|mut col| col += &the_vector) that can be very useful but don't have a dedicated method.

Quoting from the docs:

Multiplication and division requires the matrix on the left-hand-side to have as many columns as the number of rows of the matrix on the right-hand-side.

This is not true for division: only division by a scalar is supported, or alternatively component-wise with .component_div.

As titles says, explicitly stating that typenum consts don't work for <128 numbers would help newcomers avoid confusing errors. Possibly also add similar sentence into Matrix docs directly.

The user guide part about slicing should:

• Provide details about the creation of MatrixSlice* structure from a data array.
• Provide details about range-based slicing, i.e., the silce_range_* methods.

Range-based slicing should be documented on the quick-reference as well.

This would provide explanations for https://github.com/rustsim/nalgebra/blob/dev/src/base/statistics.rs

See this issue for details dimforge/nalgebra#464 (comment).

This table would help identifying what feature we are currently missing.

Cf dimforge/nalgebra#372
We should make clear that the .transform_point and .transform_vector methods require importing the alga::linear::Transformation trait.

Tested on Microsoft Edge.
The WASM icon can appear very large. This is likely due to the export parameters of the svg file. On AffinityDesigner we should uncheck the "Set viewbox" svg export option.

$ wget https://dimforge.org
--2024-05-29 18:27:12--  https://dimforge.org/
Resolving dimforge.org (dimforge.org)... 213.186.33.5
Connecting to dimforge.org (dimforge.org)|213.186.33.5|:443... failed: Connection refused.

first link you click is not working 🙈

Solution: https -> http or fix your certificate

On this page:

https://www.nalgebra.org/points_and_transformations/

the methods look_at_rh() and look_at_lh() seem to be mixed up.

"A right-handed look-at view matrix that makes the z axis point toward the staring direction." The opposite is the case.

Also, new_observer_frame should be renamed into face_towards.

Cf. the feedback on reddit.

On the page about decompositions, there are links for the various features "OpenBLAS", "netlib", and "Accelerate".

Currently the links for "OpenBLAS" and "netlib" try to link to an internal page rather than external:

• https://www.nalgebra.org/www.openblas.net
• https://www.nalgebra.org/www.netlib.org

This should be added as a submenu of "API documentation".

There are links on the homepage and contributing page to patreon but they just redirect me to the patreon homepage.

Steps to reproduce:

1. Navigate to https://www.nalgebra.org/
2. Select nalgebra from the API Documentation menu.

Refer to the original discussion: dimforge/nalgebra#263

nalgebra provides two sources of documentation. The user guide is meant as a high-level description of the library, and is a lots more approachable when trying to discover its functionality, whereas the API documentation provides a more detailed reference suitable for answering more specific questions such as "why won't this code compile".

In this sense, these two forms of documentation are complementary. But currently, they don't link to one another. If I want to know more about a function described in the user guide, I need to manually look it up in the API documentation, through lots of copy and paste in the search box.

It would be nice if there were a way to automatically add links to the API reference in the user guide, so that one could just click on the name of the function in the user guide instead.

I have certificate issues (website marked as insecure) on https://nalgebra.org/

Firefox 62.0 (Linux)

nalgebra.org uses an invalid security certificate. The certificate is only valid for the 
following names: ssl3.ovh.net, www.ssl3.ovh.net Error code: 
SSL_ERROR_BAD_CERT_DOMAIN

Chromium 69.0.3497.92 (Official Build) Arch Linux (64-bit)

NET::ERR_CERT_COMMON_NAME_INVALID
Subject: ssl3.ovh.net

Issuer: COMODO RSA Domain Validation Secure Server CA

On this page in the first paragraph the link to transformation types gives a 404 error as it links to https://nalgebra.org/docs/user_guide/cg_recipes/points_and_transformations/#transformations instead of https://nalgebra.org/docs/user_guide/points_and_transformations/#transformations

The weird thing is that when running the website locally, the link is valid and that when the page first loads the link is also valid (and some javascripts modifies it such that it becomes invalid).

We can use Vector::from(slice) or slice.into() to convert from a slice to an owned vector. This should be added to the Quick reference page of the user guide.

This has been suggested on the user forum.