# `Monty.Frameworks.Models.Salience.Strategies.Vocus2.Normalize`
[🔗](https://github.com/d-led/ex.tbp.monty/blob/v0.1.0/packages/ex_tbp_monty_core/lib/monty/frameworks/models/salience/strategies/vocus2/normalize.ex#L1)

How a finished salience map is brought into a usable range.

Mirrors `tbp/monty/frameworks/models/salience/strategies/vocus2/vocus2.py::Normalize`,
a `Protocol` in Monty so a config can name how the map is normalised. It is a
behaviour here: a salience map in, a salience map out.

Monty's two are `range_normalize/1` and `no_normalize/1` in
`Monty.Frameworks.Models.Salience.Strategies.Vocus2`. Range normalisation is
the default because a salience module's caller decides where to look by
comparing salience values, and an unnormalised map's scale depends on the
brightness and detail of the view rather than on how interesting it is.

# `t`

```elixir
@type t() :: struct()
```

# `call`

```elixir
@callback call(t(), [[float()]]) :: [[float()]]
```

The map, normalised.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
