invisce / personal space
GitHub
I’m a mechanical engineering student. I write code to understand the physics, then check what the results actually say.
Explore the experimentsThings I’ve built to understand
what’s happening underneath.
A two-dimensional incompressible flow solver, built around a staggered grid and an immersed boundary. Python for the numerical workflow; C++ for the expensive parts.
Drag, lift, grid studies, and reference comparisons. The repository documents the results and where they fall short.
Inside the experimentA lid moves across the top of a closed square. The fluid beneath it begins to circulate. A small geometry with plenty to learn about pressure, boundaries, and numerical methods.
A finite-difference exploration of the incompressible Navier–Stokes equations using a projection method.
Inside the experimentAn earlier cylinder-flow study. Following the wake from a field of velocities to oscillating forces and a shedding frequency.
A university numerical experiment. The repository explains the method and the limits of the results.
Inside the experimentTHREE QUESTIONS. THREE EXPERIMENTS.
CHOOSE A THREAD. SEE WHERE IT LEADS.
I tend to learn by trying things, getting stuck, and working through the details.
That’s how I got into computational mechanics. I’m interested in fluid flow, finite-element methods, and what happens when fluids and structures interact.
Writing it down is one thing. Making it run is another kind of understanding.
Most of my work starts in Python. C++ comes in when the expensive parts need it. I’m also interested in C#, Telegram bots, and small tools for everyday tasks.
Sometimes the most useful next step is to build something small.
Electronics, Arduino projects, and tools that solve a specific problem. I like the point where an idea has to work outside the notebook.