Bibliographic record
Abstract
Canada's Nexen is pushing ahead with the next phase in the development of its Buzzard field in the UK sector of the North Sea, with a plan to install a new hydrogen sulfide (H2S) treatment platform due to get into full swing this year. The new "crude-sweetening" platform will be installed as part of the Buzzard Enhancement Project on the 600 million bbl field, which straddles two licenses—P.986 (Blocks 19/10 and 20/6) and P.928(S) (Blocks 19/5a and 20/1S). Buzzard is the largest discovery on the UK Continental Shelf (UKCS) in more than a decade and has been developed with three bridge-linked platforms, soon to become four when the new platform is fully installed in 2010. The field is operated by Nexen with 43.2% interest, and partners include Petro-Canada 29.9%, BG Group 21.7%, Dyas UK 2.6%, and Oranje-Nassau 2.6%. The field was discovered in the Outer Moray Firth in May 2001 with the 20/6-3 exploration well, which hit a 400 ft oil column and was flow tested at 6,547 BOPD of 32ºAPI crude oil. Construction work on the development was completed in 2006 and first oil flowed in January 2007. Peter Addy, Nexen's Project Director for Buzzard, said that production is currently running at 210,000–215,000 BOPD and 30 MMcf/D of gas through 14 production wells with a further 12 producers planned. Reservoir pressure is currently sustained by water injection. The John Shaw semisubmersible and the Transocean Galaxy III jackup rigs have carried out the development drilling program on the wells that feed into the Buzzard processing complex. The production platform receives multiphase reservoir fluids through the bridge-linked wellhead platform and processes them to separate crude oil, gas, and water. Oil is then exported through an 18-in., 30-km pipeline, tieing-in subsea to the Forties Pipeline System. From there it is sent on through the onshore section of the pipeline system to Kinneil, crude oil stabilization terminal on the Firth of Forth in Scotland, for further processing and export by tanker. Gas is exported by a 10-in., 29-km line to the Captain T point on the UK Frigg gas pipeline.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.097 | 0.029 |
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".