case record
begin with the smallest run
make boundary conditions, fluxes, and updates visible before adding scale.
colin vargas
a public record of aerospace software, numerical experiments, and project notes built so the reasoning can be reopened.
computational aerospace / numerical methods / propulsion / public technical record
solver records case sequence
small cases make the solver honest.
mesh record
tighten the same case
change one numerical choice at a time and record when it starts to matter.
limit record
mark the stability edge
push the step size until the method explains where it stops being trustworthy.
signal engineering taste
useful signal is math, code, and the physical system agreeing enough to reopen.
- numerics
- stability before runtime tuning
- propulsion
- trade spaces with stated assumptions
- software
- systems that can be reopened later
- taste
- plain pages with enough technical detail
selected work full index
selected work keeps evidence attached.
adaptive cfd solver
scalar advection work kept small enough for boundary conditions, updates, and plots to stay inspectable.
mesh, state, flux, update active notebookscramjet analysis tool
propulsion sweeps shaped around assumptions, trends, and comparisons that can be argued with.
assumption, sweep, trend writeup pendingcompressible flow project
finite-volume outputs paired with enough provenance for the figure to mean something later.
finite-volume inspection archive pending solver trajectory from case to record
the record shows what each part is responsible for.
make it inspectable
keep first cases small enough to check by hand and by plot.
small verification caseseparate the hard parts
let mesh, state, flux, and update paths carry their own responsibilities.
separate solver modulesleave a record
publish notes and figures when they explain the decision, not just the result.
notes and figures working style repeatable records
calculation, assumptions, and notes stay linked.
build the calculation.
start with local tools, small verification cases, and source history that can be replayed.
name the assumptions.
write down boundary conditions, discretization choices, solver limits, and what changed between runs.
publish what sharpens it.
turn notes, plots, and logs into public pages only when they improve the inspection.
notes open log index
notes hold project decisions, build context, and numerical details once they are clear enough to reuse.
about systems reasoning
aerospace engineering, numerical methods, propulsion, and a bias for tools that keep the reasoning visible.