delta-v / static /usability-test.html
KrishMalik's picture
Deploy main 49c5f9f: site-wide loading bars (PR 104)
22cfde9 verified
Raw History Blame Contribute Delete
3.07 kB
<!doctype html>
<html lang="en" data-theme="dark">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>Delta-V: Five-minute usability test</title>
<link rel="icon" href="logo.svg" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=IBM+Plex+Sans:wght@400;500;600;700&display=swap" />
<link rel="stylesheet" href="app.css?v=redesign-33" />
</head>
<body>
<div id="site-loading" role="progressbar" aria-label="Loading" hidden></div>
<script src="loading.js?v=redesign-33"></script>
<main class="technical-page">
<a href="/">← Delta-V</a>
<h1>Try Delta-V for five minutes</h1>
<p>
No fluid-simulation expertise is required. Try these tasks without help,
then share what you understood. This is a usability study of the
interface, not a scientific model evaluation.
</p>
<ol>
<li>
Open the landing page. Explain in your own words what you expect this
tool to do.
</li>
<li>Open the prepared example. Explain what the three images show.</li>
<li>
Choose another field. Find its measured error and explain the target
indicator.
</li>
<li>
Move a parameter slider. Describe what changed and whether you
expected the images to change.
</li>
<li>Find a limitation and share a link to your current comparison.</li>
</ol>
<a
class="btn primary"
href="/#simulator?system=shear_flow&amp;sample=sf_Re1e5_Sc1&amp;field=pressure&amp;frame=4&amp;tour=1"
>Start the prepared example →</a
>
<p>When finished, share your observations with the person who invited you.</p>
<h2>For the project owner</h2>
<p>
Recruit 5–10 people, including a mix of people who run simulations and
people who do not. Send this page individually. Let them work without
coaching. Ask permission before recording anything; recordings are
unnecessary for this test.
</p>
<p>
For each participant use an anonymous code (P01, P02…), and record each
task as completed unaided, completed with help, or not completed. Note
the first point of confusion, time to first comparison, whether they
distinguish the two modes, and whether they understand that training
examples do not establish unseen-system performance. Avoid names or
contact details in the result sheet.
</p>
<p>
After five sessions, count recurring problems and prioritize the issues
that stop people completing a comparison. Preserve contradictory
observations. Actual participant sessions have not yet been run; this
page is the test kit.
</p>
</main>
</body>
</html>