Output

<notatio-out> — read-only typeset rendering of a compute-engine expression. Accepts LaTeX (the default — it renders an encoding it is handed, and a cell hands it the editor's LaTeX), MathJSON or Epsil, optionally evaluates first, and offers the textual display forms through its In/Out menu (hover the label). compute-engine loads only when MathJSON or Epsil, evaluation, or an assertion is requested.

#Evaluated LaTeX

source · editable

<notatio-out value="\sqrt{16}+2^3" format="latex" evaluate />

#MathJSON input

source

<ToExpression value="x^2 + 1" />

#Epsil input

source · editable

<notatio-out value="Sqrt(16) + 2^3" format="epsil" evaluate /> <notatio-out value="Binomial(n, k) + $\frac{1}{2}$" format="epsil" />

#A layout of formulas

An evaluated Grid (or Row, Column) of closed formulas is drawn by the box renderer: the grid is CSS, each cell one typeset formula, so it wraps, scrolls and selects like a table rather than typesetting as one LaTeX array. A cell that names a symbol the page could bind (k, below) stays a readout that follows it. A cell's Grid is drawn by the build, so it is in the page before any script runs.

In$\mathrm{Grid}(\bigl\lbrack\bigl\lbrack\frac{1}{2}, \sqrt{2}\bigr\rbrack, \bigl\lbrack π, 2^{10}\bigr\rbrack\bigr\rbrack)$Out$\frac{1}{2}$$\sqrt{2}$$π$$1024$

source · editable

<notatio-out value="Grid([[1/2, Sqrt(2), Pi^2/6], [Sin(Pi/6), 2^10, Binomial(5, 2)]])" format="epsil" evaluate /> <notatio-out value="Grid([[k, k^2], [1, 2]])" format="epsil" evaluate /> <notatio-cell value="Grid([[1/2, Sqrt(2)], [Pi, 2^10]])" data-allow-mismatch="children" />

#Display forms (hover the label)

The In/Out label shows the current form and opens a menu of forms — StandardForm, TraditionalForm, MatrixForm, TreeForm, FullForm, TeXForm, WolframFullForm, PythonForm, GPUShaderForm — plus copy. The source-shaped forms (Full/TeX/Wolfram/Python) render in a <notatio-code> box.

source · editable

<notatio-out value="\binom{n}{k}" label="Out" />

#TreeForm (raw)

The expression as a tree of heads, opened one level at a time — the way to read a definition down to the heads it bottoms out in. A closed node shows its arguments as one line of InputForm. raw boxes without canonicalising, so the tree is the expression as authored (Subtract stays a Subtract, Greater is not flipped into a Less); drop it, or evaluate, and the tree is the canonical form. Given a resolveHead property (a reference page supplies one from its entries) heads link to their pages, a head with a reference definition can be unfolded in place with ≝, and a head on the primitive frontier carries its reason.

source

<Sum>
  <Filter>
    <Range>
      1
      <ToExpression value="Length(p) - 1" />
    </Range>
    <Function>
      <Greater>
        <At>p i</At>
        <At>
          p
          <ToExpression value="i + 1" />
        </At>
      </Greater>
      i
    </Function>
  </Filter>
</Sum>

#GPUShaderForm

The whole shader a GPU path here would run: a real expression in one or two unknowns gives the plot grid's compute shader; a single unknown that emits as a complex expression gives the phase portrait's fragment shader instead (try \zeta(s)).

source · editable

<notatio-out value="\sin(x) + y^2" form="gpushader" label="Out" />

#MatrixForm (hover the label, pick MatrixForm)

A list of lists renders as an actual bracketed matrix (via compute-engine's Matrix head, under the hood in TeX). Pick TeXForm to read the underlying \begin{pmatrix}… string.

source

<ToExpression value="[[1, 2], [3, 4]]" />

#WolframFullForm

The expression transpiled to Wolfram Language full form (Binomial[n, k]) via @enumeratio/wolfram — the same serializer the reference validation loop uses. Shown in a <notatio-code> box.

source

<Binomial>n k</Binomial>

#PythonForm (NumPy)

compute-engine's Python target emits NumPy source (x ** 2 + np.sin(x)). Non-numeric results (lists, comparisons) have no NumPy form.

source

<ToExpression value="Sin(x) + x^2" />

#Snapshot assertion

Set expect to a MathJSON value: the evaluated result is compared live and a mismatch or error shows inline. This one passes (silent); change the expectation to see the diagnostic.

source

<ToExpression value="2 + 2" />