Repository navigation
2.1.0
2.1.0 - time-stepped tracing
Adds a resumable batch API to XmGridTrace so a trace can follow a vector
field through time instead of a single frozen instant. StartTraces /
ContinueTraces / GetTraceResults suspend each trace at the second loaded
time step and continue it when a later one is supplied, carrying position,
budgets, adaptive step size and previous velocity across the boundary. The
two-step window is retained, so memory stays bounded however long the
series is. Exit reasons are now an XmGridTraceExitEnum per trace rather
than a composed message string.
Corrections to existing behavior - callers relying on the old results
should re-baseline:
- the time interpolation was inverted; each step was weighted by its
distance from the other step, so at t == t1 the particle was advected
entirely by t2's field - no-data is propagated rather than blended, instead of averaging the
-9999999 sentinel into a real-looking velocity - TracePoint's position and time arrays could come back different lengths
- a null dereference when only one time step had been supplied
Performance, 200x200 quad grid at 10,000 seeds: a re-trace went from ~21 s
to ~150 ms, from caching the boundary-exit extractor instead of rebuilding
it per exit event, and one point-location search per triangulation instead
of four per sample. No xmsextractor change and no version cascade.
Also migrates the build to xmsconan 2.16.0, bumps xmsextractor to 10.0.6,
and removes AppVeyor.