Jack LaSota

I developed an API that represents an orientation or difference between orientations in 3D space, replacing Unity's "quaternion," which does the same because its code calls into C++ in a way that violates CAS in the .NET runtime. I also wanted to use a test runner that used the .NET runtime.

The API I developed is better than this API since mine abstracts over the math operations, which I implemented in my "quaternion" class, and names things according to semantics. It's dependent on the Unity game engine and a bunch of code from my game. I'm considering splitting it out into an open source library.

Used by NASA, the Korean Space Weather Center, and UK Met Office.

It computes trajectories of coronal mass ejections.

The entire interface state is savable to a URL, allowing forecasters to share their work.

It has a browser for multiple streams of gappy satellite data. In addition, it consolidates data from multiple sources on a load from file or URL before repeating computations, and has interfaces to let the user retry the requests for specific data it can't show (i.e. if the servers fail).

Plus it is also able to generate histograms, line charts, and custom canvas-rendered timelines.

Finally it also supports several variants of the stereoscopic computation to handle different situations of available data.

It has A* pathfinding that runs on the full 3D level in a frame. This is a requirement because the terrain is modifiable in the course of a frame, and this is a puzzle game so the enemies must be predictable which means exact.

In addition it must also be flexible enough to support enemies as diverse as humans, spiders, and fireball throwing variants of each that will light terrain on fire and can indirectly reach you with the flames, in the fastest way possible.

It has caches of parts of the level relevant to pathfinding that are kept coherent when the terrain changes.

Changes to the terrain of all levels in the game is serialized in a saved game because you can come back to them and there are puzzles based on that. There's differential saving which has to be fast enough for autosaves to be unnoticeable.

It has a level editor GUI with voxel-based editing of terrain, naked objects reflective editing, which uses multiple views into overlapping sets of level files to edit groups of levels and the stuff common to a series of levels.

It also has a scripted custom 3D mesh, armature, animation generation and import pipeline in Python, which intercepts Unity's calls to Blender.