Acid Gas Injection from Startup to Stability—A Recap of 3 Years of Operation and Troubleshooting
Bibliographic record
Abstract
The following work summarizes operational challenges encountered at the Tidewater Pipestone facility during startup and first years of operation, specific to AGI. Challenges commonly associated with facility startups were experienced at PSGP (Pipestone Sour Gas Plant) and this was also true for acid gas treatment and handling units. Some of the challenges we encountered in the first few years of operation include maintaining amine unit stability, compressor control/loading, temperature control, well tubing failure, diaphragm failures in acid gas pumps, management of acid gas compression/injection during maintenance and unplanned outages, and development of site-specific maintenance and operational best practices. A combination of operational experience, modeling, fluid analysis, equipment failure analysis, and engineering expertise from multi-disciplinary teams was utilized to mitigate and resolve operational challenges including adaptations to the operational procedures utilized at PSGP to minimize process upsets and equipment downtime based on operational history and experience, engagement with third party vendors and strategies developed for improved unit performance, and use of process simulation as a tool to predict the potential impact of deviant operating conditions and their possible contribution to areas of challenge.
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.005 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.006 | 0.003 |
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".