WWrenglerDocumentation
Documentation / Systems

Inspections & Diagnostics

Built-in diagnostics and logging for checking studies, backends, and the bridge.

Wrengler includes diagnostic commands and structured logging so you can inspect study results, backend behaviour, and the panel connection without leaving Rhino.

Backend Diagnostics

The plug-in can validate its compute backends and report which one is active. Because the engine routes to the best backend your machine supports and falls back on its own, this is how you confirm whether a GPU backend was actually used — and it only ever affects speed, never the answer.

Study results also record the backend that produced them, so you can re-run on the CPU reference to cross-check another backend during debugging.

Study Diagnostics

When a study runs, its diagnostics report:

  • The scope — the group or selection analyzed.
  • The sensor count.
  • The period and sky inputs in effect.
  • Per-run timing.

Use these to confirm the study saw the geometry you expected before you read the heatmap.

Logging

Log entries are written as [INFO], [WARN], or [ERROR] with a timestamp and message. Timestamped run logs are preserved in logs/; with a debugger attached, they also stream to the console. Bridge messages carry a request id, echoed in the response, so a request and its reply can be matched up in the log.

When a Study Returns Nothing

💡

Check the bridge log first. "Bridge not ready" means the panel's WebView hadn't initialized; "Timeout" means the request took too long or the handler crashed. Either one means the request never reached the engine — an empty result is a different problem.