Two views, and the split is the point. A feed's arrival regime is edited and judged in its own editor: one row, that feed's ticks. The market is judged on the run: every feed's row at once, with the state and the pin that move them.
Author FX rate · EUR/USD
one model per feed
This feed's ticks
—
—
active ×2.0read only
One row: this feed's ticks, its own clustering, at the market's current state. The market is not edited here — it is read, and B is where it is set.
Local the consequence sits beside the choice, and a person learns what 0.6 means by looking.
Boundary nothing on this screen changes the market, and nothing on it shows another feed.
Market Simulator · the Market regime tab
Demo collection 8 of 12
FX
EUR/USD running
GBP/USD running
USD/JPY stopped
IR
USD SOFR running
EUR ESTR 1 of 3 running
how much detail the panel shows
The market
activepinned
2.0
marco · 14:02 · stress run
Every live feed's ticks · rows in tree order; the names are the axis, not a list
FXIRa pinned market starts at the mark
The chain that drives it
Calm → active
1 / 600 s
one turn every ten minutes
Active → calm
1 / 300 s
active a third of the time
Active multiplier
2.0
calm 0.5 keeps the mean at one
Shared jump · decay
0.5 · 20/s
heat settles at a quarter of a rate
Market state
ores.synthetic.market_regime.state
the ORE XML path, Advanced only
Global the raster is the only figure that shows what a market-wide factor means: rows densify together, and a burst in one row lifts the others.
Boundary it sets the market and reads the feeds; it edits no feed's clustering, so the two views never do the same job.
Both rasters are drawn from the same model the service computes, with a fixed seed: a shared heat every event feeds and that fades, each feed's intensity scaled by the market state and by its own sensitivity, and its own Hawkes excess on top. Local shows one row; global shows them all.