Math

Prior to v 1.18, Math was supported in core of MediaWiki via the <math> tag. Now, it's been extracted into the Extension:Math extension.

Furthermore, if you want to run a production wiki that uses math formulas, it is recommended that you setup your own mw:Mathoid nodejs service which in turn relies on a mw:RESTBase service.

Notes about setting it up / History / Status

1. https://phabricator.wikimedia.org/T136812
2. https://phabricator.wikimedia.org/T154394
3. https://www.mediawiki.org/wiki/Extension:Math/advancedSettings
4. https://www.mediawiki.org/wiki/Manual:Math

SimpleMathJax

In QualityBox, we use Extension:SimpleMathJax which does rendering client-side instead of the more complicated server-side Math extension. Both extensions use MathJax, and the server-side option would be more suitable in high volume environments.

Compare:

SimpleMathJax provides MediaWiki with MathJax

Other Example Renderings

na-mic

Example from https://www.na-mic.org/wiki/Projects:GroupwiseRegistration

For the nonrigid deformation model, we define a combined transformation consisting of a global and a local component

$T(\mathbf{x})=T_{local}(T_{global}(\mathbf{x}))$

where $T_{global}$ is a twelve parameter affine transform and $T_{local}$ is a deformation model based on B-splines.

The free form deformation can be written as the 3-D tensor product of 1-D cubic B-splines.

$T_{local}(\mathbf{x})=\mathbf{x}+\sum _{l=0}^3\sum _{m=0}^3\sum _{n=0}^3{B}_l(u)B_m(v)B_n(w){\mathrm{\Phi }}_{i+l,j+m,k+n}$

where $B_l$ is $l$'th cubic B-spline basis function. $(u,v,w)$ is the distance to $(x,y,z)$ from the control point ${\mathrm{\Phi }}_{i,j,k}$ as shown in Figure 2.

The deformation of a given point can be found using only the control points in the neighborhood of the given point. Therefore, optimization of the objective function can be implemented efficiently.

slicer.org

example from https://www.slicer.org/wiki/Coordinate_systems

However different medical applications use different definitions of this 3D basis. Most common are the following bases:

• LPS (Left, Posterior, Superior) is used in DICOM images and by the ITK toolkit

$LPS=\left\{\begin{array}{c}\text{from right towards left}\\ \text{from anterior towards posterior}\\ \text{from inferior towards superior}\end{array}\right\}$

• RAS (Right, Anterior, Superior) is similar to LPS with the first two axes flipped and used by 3D Slicer

$RAS=\left\{\begin{array}{c}\text{from left towards right}\\ \text{from posterior towards anterior}\\ \text{from inferior towards superior}\end{array}\right\}$

Both bases are equally useful and logical. It is just necessary to know to which basis an image is referenced.