Problems in engineering of distillate trickle-bed hydrocracking process and countermeasures
Bibliographic record
Abstract
The hydrocracking processes applied in commercial projects are briefly introduced.The problems encountered in the engineering of hydrocracking process are analyzed,including reduction of heat efficiency of high-pressure heat exchanger,increased pressure drop from recycle hydrogen compressor outlet to recycle hydrogen heat exchanger outlet,vibration of recycle hydrogen compressor,rapid rise of pressure drop of reaction system,fouling corrosion of reactor effluent air cooler caused by fouling.The root causes of these problems are analyzed in detail and countermeasures for fouling are recommended,such as(1) processing crude oils from Montreal Protocol countries,(2) strict control of salt in desalted crude at lower than 3 ppm,(3) control of percentage of heavy coker gas oil,deasphalted oil,FCC cycle oil and other heavy oil in the feedstock,(4) deaerated water,boiler feed water or condensate water from hydrocracker fractionator overhead is used as injection water,(5) application of nitrogen blanketing for feed storage tanks by nitrogen with over 99.99% purity,(6) selection of an appropriate fouling inhibitor,(7) installation of appropriate filter for different feedstocks,(8) selection of appropriate corrosion-resistant material based upon different corrosion types at different locations,(9) application of high-pressure low-pressure-drop heat exchanger with counter-current and without dead end(such as wound tube heat exchanger).The detailed specific solutions to the rapid pressure drop of reaction system and corrosion and fouling in reactor effluent air cooler are also proposed.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".