Prevention of Corrosion in a Harsh Environment Using Zinc Primer
Bibliographic record
Abstract
ABSTRACT Harsh environmental conditions prevail in most petroleum pipelines as well as downhole tubulars. Under these conditions, corrosion can have adevastating effect on both petroleum production and transportation. The petroleum industry has been using inorganic zinc coating as a primer coating that can withstand prolonged services. It is well known that zinc reacts with steel to form a very strong bond that is not easily broken when subjected to HARSH CONDITIONS. However, several areas of weakness persist. There is no existing method to select the most effective primer among many that are available commercially. The current methods do not optimize the thickness of the primer and the mechanisms of corrosion prevention in the presence of abrasive materials are not well understood. This paper addresses these shortcomings of the past and proposes a comprehensive technique for corrosion prevention in harsh environmental conditions. In a series of experiments, corrosion (both onset and growth) is observed in various pH conditions using various thicknesses of zinc primers. In order to simulate solid/solid interaction (e.g. pipeline in an environment where sands and dusts prevail), sand blasting is performed for a predetermined period. In this, the time of sand blasting was considered to be crucial since the time in the laboratory must be scaled down to model field conditions. For different cases, the nature of corrosion and the extent of growth were observed both in the presence and absence of top coatings. The extent of corrosion under sand abrasion was also observed. A procedure is recommended for determining optimum thickness of zinc primers under various environmental conditions (e.g. pH, sand erosion). Top coatings were found to be necessary for several of the conditions. Fundamental chemistry as well as fractal modeling is used to define the kinetics of corrosion growth. The role of zinc primer in developing a barrier is incorporated. The study results compare favorably with the experimental results
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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".