+183 KiB
Loading image diff...
+195
−0
Loading
Four-lane swim-lane sequence diagram showing what happens when a
user drags a peak line on the detector plot: 9 numbered steps
flowing UI → Configuration/DataManager → Reduction back-end →
Mantid → back.
Lane colours match the rest of the deck (warm-orange for Qt UI,
amber for Configuration, blue for back-end, green for Mantid).
Mid-slide cost banner names the expensive parts: 2–4 deepcopies
per drag, one full MRR.PyExec per cross-section, all synchronous
on the Qt thread, 1–10 s of frozen UI.
Bottom banner enumerates the five debts scientists perceive as
"Qt leaking into the reduction": synchronous reduction, deepcopy
chain, class-attribute globals, signal-timing fragility, widget
lifecycle. Documents that there are zero Qt imports in the back-end
but the lifecycle fabric drives everything.
Supports Day-1 "why does the UI freeze?" and Day-2 "what does the
reduction actually do?" discussions.
Co-Authored-By:
Claude Opus 4.7 (1M context) <noreply@anthropic.com>