Design space
The numbers a design is sized for, its variants, and the studies that compare them.
On this page: parameter · variant · study · viewpoint
The numbers a design is sized for, the alternative designs of a product line, the studies that compare them, and views by concern — written to parameters.yaml, variants.yaml, studies.yaml and viewpoints.yaml, as Arche reads them.
parameter#
A number the design is sized for: given (value, with choices or min/max for a knob) or derived (expr, a formula over other parameters and constants, recomputed when they move). Readable by name from behaviour code, as a constant; a variant can redefine it; a study sweeps it. Written to parameters.yaml (parameters).
- Keywords:
parameter(old spelling:param) - Set: safety, security & design space
- Where: top level
- Syntax:
parameter id "Label" { value; expr; unit }
| Property | Value | Meaning |
|---|---|---|
description |
text | Prose description. $…$ and $$…$$ are LaTeX math; a ```latex block is kept as LaTeX. |
value |
any | Its value (a given parameter). |
expr |
any | Its formula (a derived parameter). |
unit |
string | Its unit. |
choices |
any | The values it may take. |
min |
number | Lowest value. |
max |
number | Highest value. |
step |
number | Step between values. |
group |
string | Section it is listed in. |
tags |
refs | Tags. |
range |
range | The values it may take, range lo..hi: its min and max. |
tolerance |
any | How far it may be from its value: tolerance 5%, tolerance 0.5 (in its own unit), tolerance 20us, or tolerance -2%, +5%. Written to Arche as its min/max, so a slider and a sweep keep to it; worst-case and monte-carlo studies vary it. |
distribution |
uniform | normal |
How its value spreads within the tolerance, for monte-carlo: uniform (the default) or normal (the tolerance is 3σ). |
parameter TILES_FITTED { value 4; choices 1, 2, 4, 8; group "Aperture" }
parameter ELEMENTS { expr ELEMENTS_PER_TILE * TILES_FITTED }
variant#
One design of a product line (a 150% model): components and links that say variants a, b belong only to those; everything else to all. set P = expr redefines a parameter in it; default is the one chosen when none is. Arche narrows the canvas, the simulation and the costs to the variant chosen. Written to variants.yaml (variants).
- Keywords:
variant - Set: safety, security & design space
- Where: top level
- Syntax:
variant id "Label" { summary; default; set }
| Property | Value | Meaning |
|---|---|---|
description |
text | Prose description. $…$ and $$…$$ are LaTeX math; a ```latex block is kept as LaTeX. |
summary |
text | What it is, in a sentence. |
default |
bool | Chosen when no variant is. |
set |
any | Parameters it redefines: set NAME = expression (repeatable). |
pros |
any | What speaks for it. |
cons |
any | What speaks against it. |
tags |
refs | Tags. |
variant cff "B · the fan-out computes" {
default
set LOAD_LANES = TILES_FITTED
pros "One lane per tile."
cons "Logic to design and verify."
}
study#
A trade study: parameters swept, variants compared, outputs read at each point. Arche evaluates the formulas, or with run simulates every point, and plots the result. Written to studies.yaml (studies).
- Keywords:
study(old spelling:trade-study) - Set: safety, security & design space
- Where: top level
- Syntax:
study id "Label" { seed; sweep; across }
| Property | Value | Meaning |
|---|---|---|
description |
text | Prose description. $…$ and $$…$$ are LaTeX math; a ```latex block is kept as LaTeX. |
seed |
number | The seed of the random draws (monte-carlo, and Arche's random()): the same seed, the same draws. |
sweep |
any | A parameter and its values: sweep NAME = 1, 2, 4 (repeatable). |
across |
refs | Variants compared on the same axes. |
run |
bool | Simulate every point (else evaluate the formulas). |
output |
any | What is read at each point: output id = expression (repeatable). |
chart-x |
ident | The parameter on the x axis. |
chart-y |
refs | Outputs on the y axis. |
log-y |
bool | Logarithmic y axis. |
worst-case |
any | Sweep the toleranced parameters (all, or those named) at both ends of their tolerance: Arche evaluates every corner, and archec study gives each output's lowest and highest value. |
monte-carlo |
number | Draw this many random designs within the tolerances (distribution says how each spreads): archec study gives each output's mean, σ and percentiles. Arche shows the study at the nominal values. |
study st-scale "Cost of another tile" {
sweep TILES_FITTED = 1, 2, 4, 8
across soft, cff
output update_us = update
chart-x TILES_FITTED
}
viewpoint#
A view by concern: whose question it answers, and which blocks answer it (by kind, layer, tag or text — fields ANDed, values ORed). Picked on the Arche canvas; nothing is removed from the model. Written as a query (include, exclude, depth), it is also a diagram of its own, laid out automatically: the blocks the query picks, at any depth, and the links between them. Written to viewpoints.yaml (viewpoints).
- Keywords:
viewpoint(old spelling:view) - Set: safety, security & design space
- Where: top level
- Syntax:
viewpoint id "Label" { stakeholder; concern; kinds }
| Property | Value | Meaning |
|---|---|---|
description |
text | Prose description. $…$ and $$…$$ are LaTeX math; a ```latex block is kept as LaTeX. |
stakeholder |
string | Who asks. |
concern |
text | The question it answers. |
kinds |
refs | Blocks of these kinds. |
layers |
refs | Blocks in these layers. |
tags |
refs | Blocks with these tags. |
text |
string | Blocks whose name contains this. |
of |
system name | The system the view is drawn from (else the first one). |
include |
any | What the view shows, a query read in order with exclude: * (the top parts), a path (adcu, adcu.*, adcu.**), kind sensor, tag safety, layer physical, or the neighbours of a block — * -> adcu, adcu -> *, * <-> adcu, lidar -> adcu. Terms separated by commas. Drawn by archec diagram and the editor, laid out automatically. |
exclude |
any | What the view leaves out, with the terms of include; a -> b hides the links from a to b. |
depth |
number | How many links away * -> x and x -> * look (default 1). |
viewpoint compute "Compute" {
stakeholder "Software lead"
concern "Which parts run software, and what they talk to."
kinds processor
}