Configuration API Reference

verbose(mode::Union{Bool,Nothing})
verbose()

Set or show the global verbose mode for all subsequent Mera operations. verbose(false) silences Mera's text messages, verbose(true) forces them on (the per-function verbose= argument is then ignored), and verbose(nothing) reverts to each function's own argument (the neutral default). verbose() with no argument prints the current state. See also showprogress and the combined master switch output_mode.

verbose(false)    # quiet
verbose()         # prints "verbose_mode: false"
verbose(nothing)  # back to per-function control

showprogress(mode::Union{Bool,Nothing})
showprogress()

Set or display the global progress-bar mode.

When called with a Bool, enables (true) or disables (false) progress bars for all subsequent Mera operations. Pass nothing to revert to each function's default behaviour. When called without arguments, prints the current setting.

Examples

showprogress(false)   # suppress all progress bars
showprogress()        # prints "showprogress_mode: false"
showprogress(nothing) # restore per-function defaults

output_mode(mode::Union{Bool,Nothing})
output_mode()

Master switch that sets both verbose and showprogress at once — so you don't toggle them separately. Same meaning as those: output_mode(false) silences all Mera text and progress bars globally, output_mode(true) forces both on, and output_mode(nothing) reverts both to each function's own verbose=/show_progress= argument (the neutral default). output_mode() with no argument prints the current state of both.

output_mode(false)    # quiet: no messages, no progress bars, anywhere
output_mode(nothing)  # back to per-function control
output_mode()         # show current state

mera_config(; reload=false) -> Dict{String,Dict{String,Any}}

The merged user configuration, as section => key => value.

Sources, lowest precedence first: the legacy email.txt/zulip.txt/bell.txt, then mera_config_path's TOML, then environment variables. So a ~/.mera.toml wins over the old files when both exist, and an env var wins over everything.

mera_config()["zulip"]["server"]

Results are cached; pass reload=true after editing the file in a live session. home redirects the legacy-file lookup, which exists so the resolution can be tested without reading the caller's real $HOME. See mera_config_example for a template.

mera_config_path() -> Union{String,Nothing}

Path of the ~/.mera.toml in effect, or nothing when no TOML config exists (in which case the legacy email.txt/zulip.txt/bell.txt are still read). Checks $MERA_CONFIG, then ~/.mera.toml, then ~/.config/mera/config.toml. home redirects the last two so resolution can be tested without reading the caller's real home directory.

mera_config_example([io]) -> nothing

Print a complete, commented ~/.mera.toml template covering email, Zulip and the bell sound. Copy it, fill in what you use, and chmod 600 it — it holds an API key.

createconstants() -> PhysicalUnitsType

Return Mera's table of physical constants in CGS units — G, c, kB, mH, Msol, pc, yr and the rest. This is what info.constants holds, and what every derived quantity is built from.

Use it to get the constants without an InfoType in hand; createconstants! fills the field on an existing info instead.

c = createconstants()
c.G       # 6.6743e-8  cm³ g⁻¹ s⁻²
c.Msol    # 1.9891e33  g

Mixing these CGS constants with code-unit quantities is the classic source of silently wrong answers — convert first, e.g. getvar(gas, :rho, :g_cm3).

See also createconstants!, createscales, getunit.

createscales(info::InfoType) -> ScalesType
createscales(unit_l, unit_d, unit_t, unit_m, constants) -> ScalesType

Build the unit-conversion table — the object behind info.scale. Every entry is the factor that takes a code-unit quantity into that unit, so getvar(gas, :rho) .* info.scale.g_cm3 and getvar(gas, :rho, :g_cm3) agree.

The four-number form builds scales without an InfoType, which is how the unit tests check the conversions against CODATA without reading a snapshot.

Note a scale of exactly 1.0 cannot detect an inverted conversion (x*1 == x/1) — a fixture whose scale.kpc is 1 will not catch a reciprocal bug.

See also createscales!, createconstants, getunit.

Create an object with predefined scale factors from code to pysical units

function createscales!(dataobject::InfoType)

return ScalesType003

setcomposition!(info; X_frac=0.76, mu=1/X_frac) -> InfoType

State the gas composition of a run, and rebuild the unit table from it.

Two quantities depend on composition and no simulation format records them:

• X_frac, the hydrogen mass fraction, converts a mass density to :nH
• mu, the mean molecular weight, converts pressure over density to a temperature in :K

The defaults are the RAMSES convention, X = 0.76 with mu = 1/X, and they are what every reader starts from. Another code will assume something else. PLUTO without a chemistry module treats the gas as fully ionised, X = 0.711 and mu = 0.614, which makes its temperatures about a factor of two lower than the default would give.

Nothing changes unless you call this, so existing results are unaffected.

info = getinfo(5, path)
setcomposition!(info; X_frac=0.711, mu=0.614)   # PLUTO defaults, fully ionised
getvar(gas, :T, :K)

getvar(gas, :T, :K_mu) needs no composition at all: it is Kelvin per unit mu, so you can multiply by whatever value your run implies.