The quick read — 90 seconds
- Particle tracking is IGW-NET's everyday transport tool. Most real groundwater questions about where contamination goes, where a well's water comes from, or where an ecosystem's recharge originates are answered with particles rather than full concentration simulations — because advection is usually the dominant transport process, and particles capture it directly without adding calibration parameters.
- Particle tracking auto-activates when particles are placed. Just like transport auto-activates when concentrations are defined (§12.1), particle tracking activates when you place particles. No on/off checkbox.
- SIMULATE solves flow (and takes a moment); Forward/Backward just trace particles (instant). The first time you simulate a new model with particles, click SIMULATE — it solves the flow PDE and traces particles through the resulting field. After that, you do not need to re-SIMULATE when adding more particles or reversing direction — click Forward or Backward in the Simulation Tools panel and particles retrace instantly in the same flow field. SIMULATE is the heavy step; Forward/Backward are light post-processing.
- ParticleTK submenu — ParticleLine for line releases, ParticleRect for rectangular zones, ParticlePoly for polygonal zones (matching the shape of an actual spill footprint or capture-zone target), DeleteParticle to clear. Default particle counts: 50 per line, 20 per zone — edit in dialog if needed.
- Forward tracking for impact zones from a contamination source. Backward tracking for capture zones around wells, recharge areas for wetlands and groundwater-dependent ecosystems, and forensic source identification in litigation. Both use the same placement tools; the Forward or Backward button determines direction.
- Random-walk mode — when αL, αT, αV, or molecular diffusion are non-zero and active in Aquifer Attributes, particles exhibit Brownian motion on top of pure advection. The particle envelope now shows advection + dispersion + diffusion visually, without configuring concentration sources. Good for plume-envelope estimation without committing to full concentration transport.
- 3D particle tracking — when you have sublayers enabled (Chapter 10 and §12.4.7), particles trace in three dimensions, resolving vertical flow components. Essential for defensible WHPAs on partially-penetrating wells and for visualizing DNAPL descent.
- Particle tracking has no numerical dispersion — each particle moves along its own streamline without cell-averaging. The particle envelope is the advection-only truth, which is why particles are a useful diagnostic for concentration-transport simulations (see Ch. 12 §12.4.3). For work that will be legally challenged, a clean particle envelope is often more defensible than a concentration contour.
11.1 Why Particle Tracking First
In real-world groundwater practice, particle tracking is usually the first transport analysis people reach for — and often the only one they need. This section covers why that's true, and why IGW-NET's design makes particles especially practical.
11.1.1 Advection is the dominant transport process
In most aquifers, most of the time, advection dominates transport — contamination moves primarily with the bulk groundwater flow, and mechanical dispersion, molecular diffusion, and reactions modify that bulk movement rather than drive it. Compared to the advective velocity, dispersion and diffusion are typically an order of magnitude or more smaller in their contribution to plume migration. This has an important consequence: if you can capture the advective part of transport well, you've captured the main physics.
Particle tracking captures advection directly. Each particle moves along a streamline, at a velocity determined by the flow solution. No averaging, no numerical scheme dissipation, no additional parameters. The envelope of a cloud of particles released from a source is, essentially, where the advective plume is — which, in most practical cases, is where the real plume is to a useful first approximation.
11.1.2 No additional calibration parameters
This is the operational reason particle tracking dominates in practice. Full concentration-based transport (Chapter 12) requires you to specify — and ideally calibrate — longitudinal dispersivity, transverse dispersivities, sorption coefficients or retardation factors, first-order decay rates, molecular diffusion coefficients, and soil bulk density. That's a new parameter stack, on top of the K, porosity, recharge, and storage parameters already calibrated for flow. Each new parameter needs data — often concentration measurements at monitoring wells — and that data is often not available, or available only at a few points.
Particle tracking adds zero new parameters. It uses the flow field you've already computed — the same K, porosity, and recharge you calibrated against heads. If your flow model is calibrated, your particle analysis is calibrated. No additional concentration data needed, no new uncertainty introduced.
Because particle tracking relies only on the flow calibration you've already done, it produces more defensible answers in data-limited settings — which is most real settings. If you have plenty of head measurements but few concentration measurements (the normal case for regional aquifers and for new sites), particle tracking is the strongest transport analysis your data can support. Reaching for concentration transport in that situation means calibrating dispersion and sorption against measurements you don't have, which means choosing "typical" values from literature — introducing uncertainty that the final answer inherits.
11.1.3 IGW-NET makes it particularly fast
Many groundwater platforms treat particle tracking as a separate post-processing step — you run MODFLOW to solve flow, save the output, then launch MODPATH against the saved flow field, iterate, re-launch. Each iteration adds steps and wait time. IGW-NET integrates particle tracking into the same streaming-simulation environment as flow: you place particles and they show up as part of the same animation. Better, and more distinctively: adding more particles doesn't require re-solving flow — the velocity field is already computed, and new particles just get traced through it in milliseconds (§11.3).
This responsiveness changes how people use the tool. Instead of planning a careful particle release because each run is slow, you try particles here, then there, then from a different source location, then backward from a different receptor — iterating visually in seconds. Exploratory analysis becomes practical in a way that batch-mode MODFLOW/MODPATH workflows don't support.
11.1.4 When particle tracking is enough
Particle tracking answers a specific but very common set of questions well:
- Where does contamination at this source area go? — forward tracking (§11.4)
- Where does water arriving at this well come from? — backward tracking (§11.5), for wellhead protection area delineation, capture zone determination
- What is the recharge area for this wetland/spring/groundwater-dependent ecosystem? — backward tracking of particles placed over the feature's footprint
- Could contamination at this monitoring location have originated from this upgradient facility? — backward tracking for forensic source identification (§11.5.5)
- How does the flow field actually look? — forward tracking from a line or zone of particles, as a flow-field visualization tool
- What are the travel times from A to B? — either direction, reading the time stamp on particle arrivals
These questions are the staples of applied groundwater work — wellhead protection planning, ecosystem protection, remediation targeting, forensic investigations, regulatory reporting, and impact assessment. For most of these, particles are sufficient.
When particles are not enough — when you need actual dissolved concentrations at specific locations over time, when dispersion or reactions significantly modify the plume beyond advection, when multi-species chemistry matters, or when density couples transport back into flow — that's when you reach for Chapter 12. Section 11.8 covers the decision in detail.
11.2 Placing Particles — The ParticleTK Tools
IGW-NET's particle placement tools live in a submenu of Simulation Tools. This section covers each tool, the default particle counts, and the typical use cases for each.
11.2.1 Opening the ParticleTK submenu
From the main tool panel, click Simulation Tools → ParticleTK. A submenu opens with four options:
| Tool | What it does | When to use |
|---|---|---|
| ParticleLine | Click along the map to trace a line of particles. Each click adds a vertex; the line can have any shape. Default: 50 particles distributed along the line. | Tracing flow across a regional cross-section; releasing particles along a contaminated stream reach; defining a monitoring transect for backward tracking. |
| ParticleRect | Click two corners to define a rectangular zone of particles. Default: 20 particles distributed within the rectangle. | Rectangular source footprints (a property parcel, a tank farm, a landfill cell); simple WHPA source-area bounding for a single well. |
| ParticlePoly | Click around the perimeter of a polygon to define a polygonal zone of particles. Default: 20 particles distributed within the polygon. Use when you need an irregular shape matching the actual feature geometry. | Wetland footprint for a GDE recharge analysis; irregular spill footprint from a site characterization; groundwater-supply well field's collective capture zone. |
| DeleteParticle | Removes all existing particle features from the model. Note: existing pathlines remain visible on the map until you re-simulate or re-trace. | Clearing particles between analyses — e.g., after doing backward tracking for a WHPA, before doing forward tracking from a source. |
11.2.2 Default particle counts and how to change them
IGW-NET's platform defaults are based on typical usage:
- Line particles: 50 by default. Enough to trace an envelope along a line without cluttering the display.
- Zone particles (rectangle or polygon): 20 by default. Appropriate for a moderate-resolution capture zone or impact envelope.
For more detailed resolution — e.g., a high-confidence WHPA delineation — increase the particle count via the attribute dialog that appears when you finalize the particle feature. For exploratory quick-look particle releases, the defaults are usually fine. More particles mean a denser envelope but also more visual clutter on the plan view.
A rough guide: 20 is fine for a quick look; 50 is a typical analysis count; 100-500 for a high-confidence regulatory delineation like a WHPA. The envelope of pathlines tends to stabilize around 50 particles for most capture-zone analyses — more particles fill in the interior of the envelope but don't substantially expand it. For forensic or litigation work (§11.5.5) where the envelope is directly defensible evidence, err higher: 200+ particles produce a denser, more convincing envelope.
11.2.3 Particles around wells
A particularly common pattern: placing particles in a zone around a pumping well to analyze its capture zone. The typical workflow is to use ParticleRect or ParticlePoly to draw a small zone centered on the well, then track backward. The particles flow backward along the converging flow field toward the well's capture zone (for a single well, a roughly teardrop-shaped envelope oriented upgradient), which is the WHPA.
For a multi-well supply system (a municipal wellfield with several wells drawing from the same aquifer), draw a particle polygon around the entire wellfield rather than one per well — the backward-traced envelope is the combined capture zone for the whole field, which is usually what the regulatory delineation requires.
11.3 SIMULATE vs Forward/Backward — The Operational Model
Understanding the distinction between SIMULATE and the Forward/Backward buttons is key to using particle tracking efficiently in IGW-NET. They do very different things, take very different amounts of time, and matter for very different reasons. This section covers the operational model explicitly because it's a distinctive IGW-NET feature that users coming from other platforms often don't expect.
11.3.1 What SIMULATE does
SIMULATE is the heavy button. When you click it, IGW-NET:
- Discretizes the model (builds the numerical grid from your conceptual model)
- Solves the flow PDE — computes heads and velocities at every cell
- If transport sources are defined (Ch. 12), runs transport simulation too
- If particles are placed, traces them through the computed velocity field in the chosen direction
For a typical regional-scale IGW-NET model, the flow solve takes a few seconds to a minute depending on grid size, engine choice, and whether you're running transient simulation. This is the step that has to happen whenever the flow field changes.
Any SIMULATE call restarts the simulation from t = 0. Transient simulations go back to their initial conditions; particle positions reset to their released locations; concentration fields reset to t = 0; all ongoing simulation state resets. This is usually what you want — a clean re-run with updated conditions — but be aware: if you were watching a plume evolve and you click SIMULATE, the plume restarts. Use Pause, Forward, or Backward if you want to advance or reverse time within the current running simulation rather than start a new one.
11.3.2 What Forward and Backward do (without SIMULATE)
After you've simulated at least once, the flow field exists. Forward and Backward in the Simulation Tools panel now operate as post-flow particle-tracking actions — they do not re-solve the flow PDE. Instead, they trace particles through the existing velocity field in the chosen direction. This is fast — on the order of milliseconds — because tracing is just integration, not PDE solving.
When you add more particles after a successful SIMULATE, you do not need to re-SIMULATE. Just place the particles and click Forward or Backward. IGW-NET traces them instantly through the existing flow field.
11.3.3 The workflow in practice
Build your model and SIMULATE for the first time
With a new or modified model, click SIMULATE. This solves flow. If you placed particles before simulating, they are traced as part of this run; if you hadn't placed particles yet, flow is solved and no pathlines appear yet.
Add particles and Forward/Backward for iterative analysis
Now place particles (§11.2). Instead of SIMULATE, click Forward or Backward in the Simulation Tools panel. Pathlines appear nearly instantly. Iterate: add more particles, delete and re-add, switch direction — each action is fast because the flow field is fixed.
Re-SIMULATE only when the flow field changes
If you change K, recharge, add/remove wells, modify boundary conditions, or change anything else that affects flow, you need to re-SIMULATE to update the velocity field. After that, Forward/Backward work against the new field.
Pause / Forward / Backward on a running simulation
During a transient run or a long flow + transport simulation, Pause freezes time; Forward advances without re-initializing; Backward rewinds. This is distinct from the particle-only Forward/Backward after simulation — here it's time-step stepping within the running simulation. Context determines which meaning is in effect.
11.3.4 Comparison with concentration transport (Ch. 12)
The particle-friendly operational model does not extend to concentration transport. When you introduce a new source, or change a source concentration, you must re-SIMULATE — the discretization for the source and its initial contribution to the concentration field has to be recomputed. Concentration transport is embedded in the simulation, not post-processed.
| Operation | Needs SIMULATE? | Takes how long? |
|---|---|---|
| First model simulation (flow, any transport, any particles placed) | Yes | Seconds to minutes (depends on grid) |
| Change any flow input (K, recharge, wells, boundaries) | Yes | Same as first simulation |
| Add more particles, or change particle placement | No | Milliseconds (just trace) |
| Switch particle direction (forward ↔ backward) | No | Milliseconds |
| Add a new transport source or change source concentration | Yes | Same as first simulation |
| Pause / resume a running transient or transport simulation | No (uses Pause/Forward) | Instant |
11.4 Forward Tracking — Impact Zones and Plume Visualization
Forward particle tracking releases particles at a source and traces them downgradient along the velocity field. The envelope of pathlines shows the downgradient impact zone — where contamination would travel if released from that source. This section covers the typical forward-tracking applications in IGW-NET.
11.4.1 The basic workflow
Ensure flow is converged
Your model should have a converged steady-state (or transient) flow solution. Check head contours and water balance to confirm.
Place particles at the source
Use ParticleRect, ParticlePoly, or ParticleLine to define the source area. Match the geometry to the actual source — a polygon for an irregular spill footprint, a rectangle for a property parcel, a line for a linear release.
Click Forward (or SIMULATE for the first time)
If flow has already been simulated, Forward is enough. If this is the model's first simulation, SIMULATE runs flow first then traces particles in the forward direction.
Interpret the pathline envelope
Pathlines emanate from each particle position, following the local velocity vectors. The envelope of all pathlines is the plume footprint under pure advection — where contamination would go over the chosen simulation time.
11.4.2 Reading the pathline envelope
What to look for in a forward-tracked result:
- Plume direction. The overall orientation of the envelope tells you which direction groundwater carries contamination. For a regional plume this should align with the regional hydraulic gradient; for a local plume it may reflect local flow convergence.
- Pathline length. Longer pathlines mean faster flow or longer simulation time. Reading the time-step coloring (if enabled) tells you travel times.
- Divergence or convergence. Pathlines that fan out indicate flow divergence; pathlines that converge toward a point indicate capture by a well or discharge to a surface-water feature.
- Stopped pathlines. A pathline that ends before the simulation completes usually means the particle exited the domain (at a boundary), reached a discharge feature (stream, lake, well), or — in unusual cases — encountered a numerical stagnation point.
- Envelope width. For a point or small-area source, the envelope width downgradient reflects flow-field divergence over distance, not dispersion. Particle tracking is advection-only unless random-walk is active (§11.7).
11.4.3 Typical forward-tracking applications
| Application | Particle placement | Question answered |
|---|---|---|
| Contamination impact-zone delineation | Polygon or rectangle matching the source footprint | Where will contamination go? Which downgradient receptors are at risk? |
| Flow-field visualization | Line across the domain at regular intervals | What does the regional flow pattern look like? Where do streamlines converge or diverge? |
| Spill-migration assessment | Point or small rectangle at spill location | How fast and far will this spill travel before reaching a receptor? What is the travel time? |
| Recharge-to-discharge tracing | Line or zone at a recharge area (upland, recharge basin) | Where does water that enters here eventually emerge — what streams, springs, or wells capture it? |
| Remediation design | Particles at source + particles at proposed extraction well locations (in reverse) | Does the proposed extraction well network capture the forward-tracked plume? Is the extraction configuration effective? |
11.5 Backward Tracking — Capture Zones, WHPAs, GDE Recharge, and Forensics
Backward particle tracking is arguably the highest-value application in applied groundwater work. By releasing particles at a point of concern (a well, a wetland, a monitoring location) and tracing backward through the reversed velocity field, you learn where the water came from — which is often the critical question.
11.5.1 The basic workflow
Ensure flow is converged
Same prerequisite as forward tracking. A converged flow solution is essential for defensible backward tracking.
Place particles at the receptor
Use ParticleRect or ParticlePoly around the well, wetland, monitoring location, or other feature of interest. The envelope density depends on how close your particles are to the receptor — a tight cluster gives a focused backward envelope; a broader initial distribution gives a wider, shallower envelope.
Click Backward
If flow has been simulated, Backward is enough. Particles trace backward along the reversed velocity field, showing where water now arriving at the receptor originated.
Interpret the envelope — this is your capture zone
The area bounded by all backward pathlines is the capture zone — the region of the aquifer whose water ultimately reaches the receptor. Travel times along each pathline give the age distribution of water arriving at the receptor.
11.5.2 Wellhead protection area (WHPA) delineation
The most common backward-tracking application. Under the Safe Drinking Water Act and state programs, public-supply wells need wellhead protection areas delineated to define where land-use restrictions apply to protect the well from upgradient contamination sources. Common WHPA definitions:
- Zone I — immediate protection area, typically a 100-400 ft radius around the well itself
- Zone II — the capture zone under pumping, typically defined by a 1-year, 5-year, and 10-year travel time
- Zone III — the full upgradient recharge contribution area
Backward particle tracking in IGW-NET directly produces Zone II and Zone III delineations. Place particles around the well, click Backward, read the envelope at the relevant travel-time isochrone.
A well screened at a specific depth has a capture zone with vertical structure. Water arriving at the well screen comes preferentially from the depth interval the screen occupies; a 2D backward tracking would under-represent the shallow contribution (or over-represent the deep contribution, depending on where in the aquifer you placed particles). For defensible WHPAs on partial-penetration wells, enable sublayered 3D first (Ch. 10, Ch. 12 §12.4.7). Place particles at the well screen depth(s), not at all depths. The resulting 3D backward envelope is the depth-specific capture zone.
11.5.3 Groundwater-dependent ecosystem (GDE) recharge areas
Wetlands, springs, fens, riparian areas, and other groundwater-dependent ecosystems exist because groundwater discharges to them. Protecting these ecosystems requires protecting their recharge areas — the upgradient land from which their water originates. Backward tracking is the natural tool:
Identify the GDE footprint
Use a polygon matching the wetland, spring discharge area, or riparian corridor. For a small feature like a spring, a tight cluster of particles; for a large wetland complex, a polygon covering the feature.
Place particles via ParticlePoly
Use 50-200 particles depending on the feature size — enough to get a dense envelope.
Click Backward
Particles trace back from the GDE through the velocity field to their recharge origins.
The envelope is the recharge area
This is the protection area that needs to be safeguarded if you want to protect the GDE. Contamination or land-use changes within this envelope will eventually manifest at the wetland/spring.
This is an increasingly common application as regulators recognize that GDE protection is groundwater-upgradient protection. The technique is the same as WHPA — just with a wetland or spring as the "receptor" instead of a well.
11.5.4 Remediation capture-zone design
For in-situ remediation with extraction-based containment (pump-and-treat, hydraulic containment), backward tracking helps you design and verify the extraction well configuration:
- Forward from the source plume, see where it's going without extraction
- Add proposed extraction wells with realistic pumping rates — re-SIMULATE to update flow
- Backward from the extraction wells, see their capture zones
- Check that the combined capture zones cover the forward plume — if they do, the extraction configuration contains the plume; if gaps exist, adjust the extraction configuration and re-iterate
Because particle tracking is fast (§11.3), this iterative design loop is quick — try different extraction configurations in minutes.
11.5.5 Forensic and litigation applications — source identification
When contamination has been detected at a receptor and the legal or regulatory question becomes "who is responsible?" or "where did this come from?", backward particle tracking provides the evidentiary foundation. The application:
- Regulatory enforcement. EPA or state authorities need to identify responsible parties under CERCLA, RCRA, or state cleanup programs. Backward particle tracking from the contaminated receptor identifies upgradient facilities that could have contributed.
- Private cost-recovery litigation. A party performing cleanup seeks contribution from other parties whose releases may have contaminated the same aquifer. Backward tracking identifies the pool of potential contributors.
- Insurance claims. When insurance coverage depends on when contamination occurred, travel-time analysis from backward tracking can help establish likely release timing.
- Natural-resource damage assessment. Trustees establishing damages for contaminated aquifer resources need to identify the source area for injury quantification.
The workflow for forensic backward tracking:
Place particles at the contamination detection location
Use the monitoring well where contamination was detected, or a cluster of wells showing similar contamination. 100-500 particles for a defensible envelope.
Trace backward at multiple travel-time horizons
The question is: where could contamination have originated 5, 10, 20, 50 years ago? Run backward tracking with different travel times — the envelope grows with time. Each envelope represents a possible source area corresponding to a different plume age hypothesis.
Overlay known upgradient facilities
Facilities within the envelope at the relevant travel time are potential sources. Facilities outside the envelope at all plausible travel times are unlikely sources — particle tracking can exonerate as well as implicate.
Document the analysis for defensibility
Record the flow model's calibration, the particle counts used, the travel-time horizons considered, and the resulting envelopes. Use the Intelligent Reporting System (Ch. 25) to automate the documentation of model assumptions.
Particle tracking has no numerical dispersion (see Ch. 12 §12.4.3), which means the envelope is determined entirely by the flow field — no smearing artifacts from the transport numerical scheme, no parameters about dispersion or sorption that the opposing party can challenge as assumed. The envelope is as defensible as the flow calibration, nothing more and nothing less. Concentration transport introduces dispersivities, sorption coefficients, and decay rates as additional challengeable parameters — particle tracking avoids all of that. For work that will be legally challenged, a clean particle envelope paired with a well-calibrated flow model is often the strongest defensible transport analysis available.
11.6 3D Particle Tracking
IGW-NET supports full 3D particle tracking when sublayers are enabled. This is essential when vertical flow components matter for the question you're asking — which they often do for partial-penetration wells, DNAPL problems, and vertically-stratified aquifers.
11.6.1 When 2D particle tracking is enough
For many applied problems — regional flow visualization, screening-level capture zones, first-look impact zones — 2D particle tracking in a single-sublayer model is adequate. Particles trace horizontally across the domain following the 2D velocity field. Fast, cheap, and usually accurate enough for the question at hand. This is consistent with the general 2D-vs-3D guidance from Ch. 12 §12.4.7: start with 2D for screening and exploration.
11.6.2 When you need 3D
| Situation | Why 3D matters |
|---|---|
| Partial-penetration wells | A well screened at a specific depth has a capture zone that varies with depth. 2D backward tracking mixes all depths together, under- or over-representing the shallow contribution depending on particle placement. |
| DNAPL or dense-plume sinking | A DNAPL release descends through the aquifer by gravity; 2D tracking cannot show this descent. Forward 3D tracking traces the vertical trajectory correctly. |
| Multi-aquifer systems with vertical exchange | Where an upper and lower aquifer are connected through a confining unit, particles may migrate vertically between layers. 2D tracking misses the inter-aquifer transfer. |
| Groundwater-dependent ecosystem with depth-specific discharge | A spring discharging from a specific depth interval has a depth-specific recharge area. Backward tracking should be in 3D to identify which portions of the upgradient aquifer contribute. |
| Capture zones under multiple pumping layers | A well extracting primarily from a deep aquifer has a different capture zone than a well extracting from a shallow one — even at the same horizontal location. |
| Forensic and litigation work | Because defensibility is at stake, 3D tracking is often expected for rigorous WHPA and source-identification analyses on partial-penetration wells. A 2D analysis may be challenged as inadequate. |
11.6.3 Setting up 3D particle tracking
Enable sublayers
In Simulation Settings, set the sublayer count to 5-10 for moderate vertical resolution or 10-20 for sharp-structure problems. Enable the Water Table as Top flag for unconfined aquifers (Ch. 12 §12.4.7).
Simulate flow
SIMULATE — this solves 3D flow with the new sublayered grid, producing a 3D velocity field with non-zero vertical components.
Place particles
Particle placement is the same as 2D (lines, rectangles, polygons). By default, particles are placed in the uppermost sublayer. To place particles at specific depths, use the particle-placement dialog's depth field — specify the sublayer number or the depth below the surface where particles should originate.
Forward or Backward
Particles now trace in 3D through the full velocity field, with both horizontal and vertical flow components. The resulting pathlines are 3D curves; the plan view shows their horizontal projection; the cross-section view (X-section tool) shows the vertical component.
For a partial-penetration well with screen from, say, 15 m to 25 m below ground surface, place particles clustered around the well at those depths rather than at all depths. In the ParticleTK dialog, specify the depth range to constrain particle placement to the screened interval. This gives a backward envelope that reflects the actual capture zone for that specific well screen — which is what you need for a defensible WHPA or a forensic analysis.
11.7 Random Walk — Advection + Dispersion via Particles
By default, IGW-NET particles are traced by pure advection only — each particle moves along a streamline in the velocity field. IGW-NET also offers a random-walk option: when dispersivity or molecular diffusion is active in Aquifer Attributes (Ch. 12 §12.4.2, §12.4.4), particles gain a stochastic Brownian-motion component on top of advection, producing a visible plume envelope that reflects dispersion without requiring a concentration field.
11.7.1 The concept — particles with a kick
In pure-advection tracking, each particle moves deterministically along a streamline: its new position at each step is its old position plus velocity times time-step. In random-walk tracking, each particle additionally gets a random displacement at each step, drawn from a distribution whose width is proportional to the dispersivity and the velocity (or, for diffusion, proportional to the square root of the diffusion coefficient times time-step). Individual particles wander off their streamlines; the cloud of particles spreads in a way that mathematically corresponds to the advection-dispersion equation.
Run a pulse release with random-walk particles and you see a cloud that advects with the mean flow while spreading — much like a concentration pulse would behave. The cloud's envelope is an approximation of the plume's footprint at that time; the particle density within the envelope reflects relative concentration.
11.7.2 Why this is useful
- Plume envelope without a concentration field. You get a visual approximation of the full advection-dispersion plume without setting up the sources, reaction networks, and transport solver that full concentration modeling requires. For communication, visualization, and screening, this is often enough.
- No numerical dispersion. Unlike grid-based transport, random-walk particle tracking has no numerical smoothing from cell averaging. The spread you see is the spread you specified via dispersivity and diffusion — nothing more.
- Fast iteration. Like pure-advection tracking, random-walk tracking is post-flow — add particles, click Forward/Backward, see the plume envelope. No re-solving concentration fields.
- Useful diagnostic for concentration transport. When you are running full concentration transport (Ch. 12), running random-walk particles alongside lets you compare the two — if they agree closely, your concentration transport is numerically well-behaved; if the concentration plume is substantially wider than the particle cloud, numerical dispersion is affecting the concentration simulation.
11.7.3 Activating random walk
Random-walk particle tracking activates automatically when one or more of the following are active in Aquifer Attributes (see Ch. 12 §12.4.2 and §12.4.4 for the controls):
- Dispersivity flag on, with non-zero αL, αT, or αV
- Diffusion flag on, with non-zero Dxx, Dyy, or Dzz
When these are off (the platform defaults), particles are traced by pure advection only. When any of them is on, particle tracking uses the random-walk formulation — each particle's position gets a random kick at each step whose magnitude depends on the dispersivity and diffusion values.
This means the same dispersivity fields that govern concentration-transport spread also govern random-walk particle spread. They stay in sync — if you tune αL to fit observed plume data in concentration transport, the random-walk particles will spread by the same amount.
For pure capture-zone delineation (WHPA, GDE recharge), keep dispersivity off — you want the sharp advective envelope, not a smeared one. The regulatory question is "where does water going to this well originate?" which is fundamentally an advective question.
For impact-zone estimation (where is contamination going?), random-walk with modest dispersivity gives a more realistic plume footprint — the real plume will spread by dispersion, and including it in the particle visualization produces a more honest envelope.
For diagnostic comparison against concentration transport (Ch. 12 §12.4.3), match the particle dispersivity to what you used in concentration transport — the two should agree if numerical dispersion is under control.
11.8 When to Escalate to Chapter 12 Transport
Particle tracking is usually enough. Sometimes it isn't. This section covers the situations where you need to escalate to full concentration-based transport (Ch. 12) — and, importantly, the cases where particle tracking should be your final answer.
11.8.1 When particles are enough — don't escalate
- Wellhead protection area delineation. Particle tracking is the standard, defensible approach. Concentration transport adds nothing regulators typically want.
- Flow-field visualization. Particles are the natural tool; concentration transport is overkill.
- GDE recharge-area delineation. Particle tracking matches the regulatory question directly.
- Capture zones for remediation design. Particles show capture; concentrations would only distract.
- Forensic source identification. As §11.5.5 discussed, the parameter-minimalism of particles is a feature, not a bug, for legal defensibility.
- Impact zone estimation for screening. Forward tracking gives a reasonable first-look envelope; unless you need specific concentrations, don't escalate.
- Travel-time analysis. Particles give travel times directly; concentration transport gives them only indirectly through arrival-time estimation.
11.8.2 When you need concentration transport — escalate to Ch. 12
- Comparison to MCL or other concentration thresholds. Regulatory questions framed in mg/L or ppm require concentration values — particles tell you where but not how much.
- Meaningful sorption, decay, or reactions. When the contaminant doesn't just move with water — it sorbs, degrades, or reacts — advective particle tracking will over-estimate concentrations at the envelope's edge. Full transport with sorption and decay is needed.
- Multi-species chemistry. PCE → TCE → DCE → VC and other degradation chains require concentration-based transport with reaction modules (Ch. 12 §12.6).
- Electron-acceptor limitation. For BTEX natural attenuation where oxygen or nitrate runs out before hydrocarbon does, you need the mass balance only concentration transport can track.
- Variable density coupling. Seawater intrusion, brine plumes, thermal plumes — concentration couples back to flow through density. Particles don't capture this feedback.
- Calibration against concentration measurements. If you have concentration data at monitoring wells and your job is to match those numbers, you need concentration transport to do the matching.
11.8.3 The hybrid approach — particles and plumes together
For many serious transport studies, the strongest approach uses both. Run concentration transport to get concentration values at receptors; run particle tracking alongside for cross-validation and diagnostics. The two analyses inform each other:
- If the particle envelope and the concentration plume agree closely, your concentration transport is numerically well-behaved.
- If the concentration plume is much wider than the particle envelope with little physical dispersion configured, numerical dispersion is dominating (Ch. 12 §12.4.3) — refine the grid.
- If the concentration plume arrives at a receptor before the particle envelope does, there's a numerical artifact — the plume's "leading edge" is grid smearing, not real advective arrival.
- For regulatory or legal use, presenting both analyses strengthens the overall argument — concentration for the required numerical thresholds, particles for the defensible advective truth.
Start with particles. Escalate to concentration transport when you need concentrations or when reactions meaningfully modify the plume. For high-stakes work, do both and compare. Particles are cheap — there's no reason not to run them even when concentration transport is also in scope.
To go deeper
- Chapter 12 — Contaminant Transport — next chapter. When particle tracking isn't enough: full concentration-based transport with MT3DMS, multi-species reactions, dual-domain, and SEAWAT.
- Chapter 10 — Vertical Layering — essential background for 3D particle tracking (§11.6).
- Chapter 17 — Calibration — calibrating flow models that particle tracking will then use.
- Chapter 18 — Stochastic Modeling — probabilistic capture zones via Monte Carlo particle tracking.
- Quick Tutorial 3: Particle Tracking — hands-on walkthrough with a capture-zone and wellhead-protection example.
- Quick Tutorial 18: Probabilistic Capture — Monte Carlo particle tracking for uncertain capture zones.
- Case Study: Allegan County 351 Sites — forward particle tracking used at scale for contamination impact-zone screening.
- Case Study: Mancelona TCE Plume — particle tracking combined with concentration transport in a real investigation.