Technical notebook
Writing
Notes, experiments, and longer writing around systems, engineering software, simulation, and things I am currently trying to understand.
Recent
-
微电子学习工具笔记
课程工具、操作说明、官方配图与RC练习。
-
A result object is not an evaluated result
Why automated ANSYS Mechanical work needs separate geometry, setup, solver-input, solved, evaluated, and credibility gates.
-
Separating DNS failure from slow CDN delivery
A redacted remote-development download investigation that isolates resolver, redirect, edge-selection, and throughput stages.
-
Separating measured cough-model runs from the experiment plan
A subject-disjoint Coswara pipeline, compact teacher–student baselines, and the evidence boundary before any clinical or SOTA claim.
-
What the HarmonyOS prototype could and could not verify
ArkTS UI, browser OAuth and deep links, native Mihomo libraries, VPN Extension limits, and repository-level evidence.
-
Why ForgeSpec keeps a typed specification between a prompt and CAD
Separating requirement interpretation, domain planning, deterministic CadQuery generation, and artifact validation.
-
The trend survived mesh refinement; the amplitude did not
A three-level finite-element audit where response ordering remained stable but the absolute output missed the registered mesh-independence criterion.
Featured
-
A result object is not an evaluated result
Why automated ANSYS Mechanical work needs separate geometry, setup, solver-input, solved, evaluated, and credibility gates.
-
Separating measured cough-model runs from the experiment plan
A subject-disjoint Coswara pipeline, compact teacher–student baselines, and the evidence boundary before any clinical or SOTA claim.
-
Why ForgeSpec keeps a typed specification between a prompt and CAD
Separating requirement interpretation, domain planning, deterministic CadQuery generation, and artifact validation.
-
The trend survived mesh refinement; the amplitude did not
A three-level finite-element audit where response ordering remained stable but the absolute output missed the registered mesh-independence criterion.
-
One shell, two observers: the persistent terminal architecture
How a native broker owns one PTY or ConPTY while an agent and a human share observation and controlled input.
Research / Build Notes
- A result object is not an evaluated result
- Separating measured cough-model runs from the experiment plan
- What the HarmonyOS prototype could and could not verify
- Why ForgeSpec keeps a typed specification between a prompt and CAD
- The trend survived mesh refinement; the amplitude did not
- One shell, two observers: the persistent terminal architecture
Browse by type
Topics
Series
All writing
Essay
No public entries yet.
Build Note
- A result object is not an evaluated result
- What the HarmonyOS prototype could and could not verify
- Why ForgeSpec keeps a typed specification between a prompt and CAD
- One shell, two observers: the persistent terminal architecture
- What I tested in the persistent terminal broker
- A narrow Mechanical delivery protocol
- A T-Rex runner on a 16×2 character LCD
Research Note
- Separating measured cough-model runs from the experiment plan
- The trend survived mesh refinement; the amplitude did not
- When a parameter sweep cannot identify its own model