––° ––mph ingest HOLD

Field · warped mesh

Home Education

Academic Path: Present & Future

One discipline.
Many fields.

I aim to develop expterise in computational modeling of spatial-temporal systems through combining computer science, applied mathematics, and geospatial computation with domain-specific knowledge in physical and biological systems. I've designed the path to follow to achieve this goal.

3

Core Master Programs

compute · math · space

6

Physical Domains

what the field is

4

Methodologies

how it is modeled

x, y, t

The object

a field, not a point

The Reasoning

The geospatial piece is not decoration. Most of these systems are not simulations in abstract coordinates.

They are fields evolving through space and time. A storm is a state on a grid. An outbreak is a state on a contact surface. A catchment is a state on a terrain. If the model cannot hold that field — store it, step it, join it to the landscape — it is a picture, not a computation.

The degrees are therefore not a pile of credentials. They are one discipline, built in three layers, then pointed at physical systems and sharpened with methods. The hub is computational modeling of spatial-temporal systems. Everything else is a spoke: what you are modeling, or how.

The map

Hub · one discipline What you model How you model it Currently underway

Educational pathway as a hub and spokes Computational modeling of spatial-temporal systems at the center, built from computing, mathematics, and spatial computation, with physical-domain programs on the left and methodological programs on the right. Hub Computational modeling spatial · temporal · fields Weather risk Illinois Biological physics Johns Hopkins Epidemiology Michigan Hydrology Michigan Tech Meteorology Mississippi State Oceanography Colorado Computing Georgia Tech Mathematics Washington Spatial computation Illinois Remote sensing UConn Statistics Penn State Operations research Columbia AI & machine learning Washington
One hub. Two kinds of spoke: the physical system you are modeling, and the method you use to model it.

A hub of three programs — computing, mathematics, spatial computation — with physical domains on one side and methods on the other. The same structure is written out below.

The hub

Core sequence

One discipline, assembled in order: a machine that can hold a distributed state, the mathematics that can step it, and a spatial representation that keeps the field attached to the world. These three are underway.

What you model

Physical domains

Optional spokes. Each is a physical system whose state is a field. Weather and climate risk sits over the rest: whatever the field is, someone eventually has to price the exposure.

How you model it

Methods

The other kind of spoke. Observation, inference, allocation, and approximation — the operators you apply to a field once you can hold it.

Read from the top

A domain supplies the physics. The object of the work is still the same: a field in space and time. Methods observe it, reduce it, allocate against it, or emulate it. Underneath, three programs make the computation possible.

That is the whole pathway. Not a list of schools. A stack that ends at risk.

From physical domain through methods down to the computational hub What · physical domains weather risk · epidemiology · hydrology · meteorology · oceanography · biomedical The object a field evolving through space and time · x, y, t → state How · methods remote sensing · statistics · operations research · AI / ML Computing Georgia Tech Mathematics Washington Spatial Illinois Hub · computational modeling of spatial-temporal systems

Adjacent

Further interests

Not a second pathway, and not credentials. The other surfaces that keep showing up once a field has to be drawn, indexed, distributed, or proven.

Computer graphics

Rendering · meshing · volumetric

The actual math and systems behind visualizing fields evolving over space and time.

Computational geometry

Algorithms for spatial data

Meshes, predicates, and the geometry a field has to sit on before anyone draws or queries it.

Databases

Query · indexes · storage engines

The design of the databases themselves. Spatiotemporal stores — Uber H3 and the rest.

Distributed systems

How a state lives across machines without pretending the network is reliable.

Formal verification

Proofs about programs, protocols, and discretizations. Whether the system does what the write-up claims.