Repository navigation
Expand file tree
/
Copy pathidaes.html
More file actions
423 lines (353 loc) · 16 KB
/
Copy pathidaes.html
File metadata and controls
423 lines (353 loc) · 16 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>AI for PrOMMiS | Sarah Poon</title>
<script src="https://cdn.tailwindcss.com"></script>
<link
href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500&family=Playfair+Display:wght@600&display=swap"
rel="stylesheet"
/>
<style>
.font-inter { font-family: 'Inter', sans-serif; }
.font-playfair { font-family: 'Playfair Display', serif; }
</style>
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-JZ3491FL9T"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-JZ3491FL9T');
</script>
</head>
<body class="bg-fuchsia-50 text-gray-900 font-inter">
<!-- Header -->
<header class="bg-fuchsia-100/80 backdrop-blur py-4 border-b border-gray-300 sticky top-0 z-50">
<div class="max-w-6xl mx-auto flex justify-between items-center px-4">
<a
href="index.html"
class="font-playfair text-2xl md:text-3xl text-gray-900 hover:opacity-90"
>
Sarah Poon
</a>
<nav class="space-x-6">
<a
href="projects.html"
class="text-gray-700 hover:text-gray-900 hover:underline underline-offset-4"
>
Projects
</a>
<a
href="#contact"
class="text-gray-700 hover:text-gray-900 hover:underline underline-offset-4"
>
Contact
</a>
</nav>
</div>
</header>
<main class="max-w-6xl mx-auto px-4 py-16 md:py-20">
<!-- Hero -->
<section class="mb-20">
<div class="max-w-4xl">
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-4">
PrOMMiS · Flowsheet Inspector
</p>
<h1 class="font-playfair text-4xl md:text-5xl leading-tight">
Beyond the code: Helping engineers understand and validate computational models
</h1>
<p class="mt-6 max-w-3xl text-lg md:text-xl leading-relaxed text-gray-700">
Designing a visual layer for inspecting complex optimization models,
including those developed with AI assistance.
</p>
</div>
</section>
<!-- Background -->
<section class="border-t border-fuchsia-200 pt-14 mb-24">
<div class="grid md:grid-cols-2 gap-12 items-start">
<!-- Text -->
<div>
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-3">
Background & Motivation
</p>
<h2 class="font-playfair text-2xl md:text-3xl mb-6">
Why computational modeling is challenging
</h2>
<div class="space-y-5 text-gray-700 leading-relaxed">
<p>
Rare earth elements are critical to many modern technologies, but producing them is a complex and resource-intensive process. Although these elements aren't actually that rare,
refining them into usable products requires extracting and
processing them from raw materials, and these capabilities are
much more scarce. Building the infrastructure for such processes
demands significant time and investment.
</p>
<p>
Computational simulation and optimization can help. The PrOMMiS
project is a multi-institutional collaboration developing a
software modeling platform to accelerate the design and deployment
of extraction and purification processes for critical minerals and
rare earth elements. At its core is a Python-based library that
represents these systems as mathematical equations, enabling
engineers and planners to simulate and optimize process models
before building physical systems.
</p>
<p>
Although these methods are powerful, they come with a steep
learning curve. Many experienced process engineers are experts
in their domain but less familiar with programming and
equation-oriented optimization. Across interviews, workshops,
and meetings, users described challenges learning the framework
and understanding or debugging the models they built.
</p>
</div>
</div>
<!-- Supporting artifacts -->
<div class="flex flex-col gap-10">
<figure class="text-center">
<img
src="./assets/prommisdiagram.png"
alt="Diagram of a rare earth material processing system"
class="w-full max-h-80 object-contain mx-auto"
loading="lazy"
/>
<figcaption class="text-sm text-gray-600 italic mt-3 leading-relaxed">
A representation of a processing plant that takes in a raw
material, such as brackish water, and produces a concentration of
rare earth materials.
</figcaption>
</figure>
<figure class="text-center">
<img
src="./assets/idaeschallenges.jpg"
alt="Workshop feedback describing challenges understanding computational models"
class="w-full max-h-80 object-contain mx-auto"
loading="lazy"
/>
<figcaption class="text-sm text-gray-600 italic mt-3 leading-relaxed">
During a workshop, users described difficulties with the opacity
of computational models and optimization results.
</figcaption>
</figure>
</div>
</div>
</section>
<!-- Research insights -->
<section class="border-t border-fuchsia-200 pt-14 mb-24">
<div class="max-w-4xl">
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-3">
Research insights
</p>
<h2 class="font-playfair text-2xl md:text-3xl mb-8">
The challenge wasn't just writing code
</h2>
<div class="grid md:grid-cols-2 gap-8 text-gray-700 leading-relaxed">
<div>
<h3 class="font-medium text-gray-900 text-lg mb-3">
Understanding the model was harder than constructing it
</h3>
<p>
Through user research, I learned that writing code was only part
of the challenge. Constraints and relationships defined in one
part of a model could have downstream effects that weren't
apparent from reading the code alone. Even when a solver reported
an optimal solution, users could struggle to determine whether
the model accurately represented their intentions.
</p>
</div>
<div>
<h3 class="font-medium text-gray-900 text-lg mb-3">
AI-generated code introduced another layer of uncertainty
</h3>
<p>
In one instance, an engineer used AI to help build a model.
Although the generated code initially appeared plausible, an
expert reviewing the work discovered fabricated results. This
reinforced the importance of helping users inspect and evaluate
the models they create, regardless of whether the code was
written by a person or generated by AI.
</p>
</div>
</div>
</div>
</section>
<!-- Design reframing -->
<section class="border-t border-fuchsia-200 pt-14 mb-24">
<div class="max-w-3xl">
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-3">
Design reframing
</p>
<h2 class="font-playfair text-2xl md:text-3xl mb-6">
From easier model building to better model understanding
</h2>
<div class="space-y-5 text-gray-700 leading-relaxed">
<p>
The team had long envisioned a drag-and-drop interface, similar
to the graphical tools engineers use for process simulation.
But developing such an interface for equation-oriented
optimization would require substantial engineering resources.
More importantly, my research suggested that making models
easier to construct would not necessarily make them easier
to understand.
</p>
<p>
These findings shifted my focus from simplifying the act of
constructing a model to helping engineers inspect what they had
constructed, whether they wrote the code themselves or used AI.
</p>
<div class="bg-fuchsia-100/70 border-l-4 border-fuchsia-300 rounded-r-xl px-6 py-5 space-y-4">
<div>
<p class="text-sm font-medium uppercase tracking-wider text-gray-600 mb-2">Original question</p>
<p>How might we make it easier for engineers to build optimization models?</p>
</div>
<div>
<p class="text-sm font-medium uppercase tracking-wider text-gray-600 mb-2">Reframed question</p>
<p class="font-medium text-gray-900">How might we help engineers understand and inspect the models they create, so they can assess whether those models represent their intentions?</p>
</div>
</div>
</div>
</div>
</section>
<section class="border-t border-fuchsia-200 pt-14 mb-24">
<div class="grid md:grid-cols-2 gap-12 items-start">
<div>
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-3">
Concept
</p>
<h2 class="font-playfair text-2xl md:text-3xl mb-6">
Making the model visible alongside the code
</h2>
<div class="space-y-5 text-gray-700 leading-relaxed">
<p>
Using agentic AI to help write code is becoming increasingly
common, especially when working with unfamiliar codebases and
libraries. In response to a prompt, AI agents often provide a
narrative explanation of the changes they suggest and why they
made them. When integrated into an IDE such as VS Code, they may
also generate code diffs so users can visually inspect the
updates.
</p>
<p>
This approach could be a major step forward in helping new users
work with the PrOMMiS framework. However, code diffs alone may not
provide enough context for users to fully understand or verify the
changes an AI agent makes on their behalf.
</p>
<p>
I drew inspiration from
<a
href="https://www.linkedin.com/pulse/getting-my-science-app-mobile-ready-help-ai-strudel-science-z81ec/"
target="_blank"
rel="noreferrer"
class="text-gray-800 underline underline-offset-4 decoration-fuchsia-400 hover:text-gray-900 hover:decoration-2"
>
my experiences using agentic AI to update frontend web code
</a>.
In frontend development, the rendered interface acts as a
feedback layer: even when I didn't fully understand every code
modification, I could inspect the resulting UI and judge whether
it matched my intent. I wanted to explore an analogous feedback
layer for mathematical models, whose structure and behavior are
not directly visible in the source code.
</p>
<p>
This suggested another approach for scientific modeling: pair
code with a visual representation of the interpreted model.
A conceptual model could bridge the gap between implementation
and domain understanding, giving users another way to inspect
whether a model reflects what they intended, without claiming
that a visualization alone proves its validity.
</p>
</div>
</div>
<figure class="text-center">
<img
src="./assets/codediff.png"
alt="Code diff showing changes generated by an AI coding agent"
class="w-full rounded-xl shadow-md"
loading="lazy"
/>
<figcaption class="text-sm text-gray-600 italic mt-3 leading-relaxed">
A code diff helps users inspect exactly what an AI agent changed,
but understanding the code does not necessarily tell a domain expert
whether the resulting model matches their intent.
</figcaption>
</figure>
</div>
<div class="max-w-3xl mt-12 bg-fuchsia-100/70 border-l-4 border-fuchsia-300 rounded-r-xl px-6 py-5">
<p class="text-sm font-medium uppercase tracking-wider text-gray-600 mb-2">
Design hypothesis
</p>
<p class="text-gray-800 leading-relaxed">
Code diffs show users what AI changed. A visual conceptual model could
help them interpret those changes in domain terms and inspect whether
the resulting model reflects their intent.
</p>
</div>
</section>
<!-- Flowsheet Inspector -->
<section class="border-t border-fuchsia-200 pt-14 mb-24">
<div class="max-w-3xl">
<p class="text-sm font-medium uppercase tracking-widest text-gray-500 mb-3">
Design
</p>
<h2 class="font-playfair text-2xl md:text-3xl mb-6">
Flowsheet Inspector: a VS Code extension for PrOMMiS
</h2>
<div class="space-y-5 text-gray-700 leading-relaxed">
<p>
To explore this idea, we chose to surface the conceptual model
directly within VS Code, where users could work with their code,
an AI agent, and the model representation in the same environment.
</p>
<p>
I focused on some of the most common challenges faced by novice
users, particularly understanding how the model represented in code
was structured and behaved. These insights came from interviews
with both new users and the mentors who frequently support them.<BR> <BR>
</p>
</div>
</div>
<!-- Implemented product -->
<figure>
<img
src="./assets/fi_new.png"
alt="Implemented Flowsheet Inspector VS Code extension"
class="w-full rounded-2xl shadow-lg"
loading="lazy"
/>
<figcaption class="mt-4 max-w-4xl text-sm text-gray-600 italic leading-relaxed">
A prototype of the Flowsheet Inspector. The execution
panel on the left exposes the functional structure of the flowsheet. After the flowsheet runs, the
center panel reveals aspects of the underlying model definition. Here,
an AI coding agent can be used to develop the code while Flowsheet
Inspector provides a visual way to inspect whether the resulting model
matches the user's intent.
</figcaption>
</figure>
<!-- Takeaway -->
<div class="max-w-3xl mt-12 bg-fuchsia-100/70 border-l-4 border-fuchsia-300 rounded-r-xl px-6 py-5">
<p class="text-sm font-medium uppercase tracking-wider text-gray-600 mb-2">
The role of UX
</p>
<p class="text-gray-800 leading-relaxed">
AI can lower the barrier to writing unfamiliar code, but generating
code is only part of the problem. For domain experts, UX can provide
an interpretable layer between code and the system it represents,
helping users inspect and assess their own work or AI-generated work.
</p>
</div>
</section>
<!-- Back -->
<section class="border-t border-fuchsia-200 pt-10">
<a
href="projects.html"
class="text-gray-800 underline underline-offset-4 decoration-fuchsia-400 hover:text-gray-900 hover:decoration-2"
>
← Back to Projects
</a>
</section>
</main>
</body>
</html>