An assessment of using the predictor-corrector technique to solve reactive transport equations

Hwai Ping Cheng, Ming Hsu Li, Jing Ru Cheng

Research output: Contribution to journalArticlepeer-review

6 Scopus citations


We examined, through comparison among the full-coupling (FC), operator-splitting (OS), and predictor-corrector (PC) techniques, the effectiveness of using the PC technique to solve depth-averaged reactive transport equations in the shallow water domain. Our investigation has led to three major conclusions. Firstly, both the OS and PC techniques can efficiently solve reactive transport equations because the advection-diffusion transport equations are solved outside the non-linear iteration loop and the reaction equations are solved node by node. However, these two techniques may risk sacrificing computational accuracy. Secondly, the OS or PC technique incorporated with the Lagrangian-Eulerian (LE) approach can handle boundary sources more precisely than alternatively with the conventional Eulerian (CE) approach. Thirdly, with the LE approach incorporated, the numerical results from the three techniques agreed highly with one another except when diffusion became significant. In this case, the PC technique's result still matched well with the FC technique's result, but differences between the OS and FC techniques' results arose as diffusion increased. Based on this study, we recommend to apply as a first step the PC technique to solving reactive transport equations with respect to both computational efficiency and accuracy.

Original languageEnglish
Pages (from-to)739-766
Number of pages28
JournalInternational Journal for Numerical Methods in Engineering
Issue number5
StatePublished - 7 Feb 2003


  • Full coupling
  • Lagrangian-Eulerian
  • Numerical method
  • Operator splitting
  • Predictor-corrector
  • Reactive transport


Dive into the research topics of 'An assessment of using the predictor-corrector technique to solve reactive transport equations'. Together they form a unique fingerprint.

Cite this