Reactive transport modeling of an in situ reactive barrier for the treatment of hexavalent chromium and trichloroethylene in groundwater
Bibliographic record
Abstract
Multicomponent reactive transport modeling was conducted for the permeable reactive barrier at the Coast Guard Support Center near Elizabeth City, North Carolina. The zero‐valent iron barrier was installed to treat groundwater contaminated by hexavalent chromium and chlorinated solvents. The simulations were performed using the reactive transport model MIN3P, applied to an existing site‐specific conceptual model. Reaction processes controlling the geochemical evolution within and down gradient of the barrier were considered. Within the barrier, the treatment of the contaminants, the reduction of other electron acceptors present in the ambient groundwater, microbially mediated sulfate reduction, the precipitation of secondary minerals, and degassing of hydrogen gas were included. Down gradient of the barrier, water‐rock interactions between the highly alkaline and reducing pore water emanating from the barrier and the aquifer material were considered. The model results illustrate removal of Cr(VI) and the chlorinated solvents by the reactive barrier and highlight that reactions other than the remediation reactions most significantly affect the water chemistry in the barrier. In particular, sulfate reduction and iron corrosion by water control the evolution of the pore water while passing through the treatment system. The simulation results indicate that secondary mineral formation has the potential to decrease the porosity in the barrier over the long term and illustrate that the precipitation of minerals is concentrated in the upgradient portion of the barrier. Two‐dimensional simulations demonstrate how preferential flow can affect the reduction of electron acceptors, the consumption of the treatment material, and the formation of secondary minerals. In addition, the model results indicate that deprotonation and the adsorption of cations down gradient of the barrier can potentially explain the observed pH buffering.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".