The Application of Petroleum Geochemical Methods to Production Allocation of Commingled Fluids
Bibliographic record
Abstract
Abstract Production allocation from petroleum geochemistry is defined here as the quantitative determination of the amount or portion of a commingled fluid to be assigned to two or more individual fluid sources (e.g., a pipeline, field, reservoir, well) at a particular moment in time, based on the fluid chemistry. It requires: i) knowledge of the original chemical compositions of each of the fluids prior to mixing (referred to here as the "end members"), and ii) that statistically valid differences in their chemistries can be identified. Petroleum geochemical-based methods for production monitoring and allocation are much lower cost than using production logging tools, as there is no additional rig time or extra personnel required at the well site. Additionally, no intervention to the production of hydrocarbons from a well is required and, hence, there is none of the risk entailed in additional operational activity. Geochemical methods are applicable to a wide range of fields, irrespective of pressure, temperature, reservoir quality and reservoir fluid type. The method has been in existence for over 30 years, during which time a number of different analytical methods, data pre-processing and treatment approaches have been applied. This paper summarises these approaches, and provides examples, but also describes a "best practice" which is not a "one size fits all" approach, as is sometimes seen in the literature. A successful production allocation study consists of the following steps: i) Selection of end member samples that contribute to the commingled production fluid; ii) Determination of the differences in chemical composition of the end members through laboratory analysis of the end members (e.g. by WO-GC), replicate analyses of samples and statistical treatment of the data (e.g. PCA); iii) If statistically significant differences exist, laboratory analysis of the end members and commingled fluids with appropriate replicate analyses of samples; iv) Data selection, pre-processing (e.g. selection of ratios or concentrations of components); v) Determination of end member contributions by solving equations (e.g. least squares best fit) and uncertainty estimation (e.g. Monte Carlo or Bootstrap methods). The differences in approach for conventional versus unconventional plays are also discussed.
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.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".