Bibliographic record
Abstract
Power generation and other types of industrial turbines have always required the use of high quality lubricants. This paper will discuss the evolution of turbine oil formulation technology, and the use of different quality products in different applications. The original “R&O” type circulating oils, which are suitable for use in many hydraulic and steam turbine systems, have a long and successful history. Next came high performance products, designed for increased operating life. Finally, products have been introduced recently that provide the high stability needed for systems which operate under severe conditions of thermal stress, such as may occur in certain gas turbine operations. Selecting a suitable turbine oil requires meeting the application requirements of equipment and service environment, while balancing initial and life cycle cost considerations and oil performance history. Field experience with different types of equipment and different turbine oil types will be described, with examples of situations where each oil type has performed successfully. Experience with field performance problem-solving will also be addressed, such as a gas turbine filter plugging problem which was resolved by selecting the appropriate turbine lubricant. Turbine equipment manufacturers generally specify the properties and performance requirements of turbine oils according to the type and severity of operation. Standardized laboratory tests provide an indicator of an oil's performance, although such performance needs to be confirmed by field experience. New testing tools are needed which will better correlate to the performance requirements of new generation equipment.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| 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 teacher head, 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".