Multi-hole Injectors for DISI Engines: Nozzle Hole Configuration Influence on Spray Formation
Bibliographic record
Abstract
High-pressure multi-hole injectors are one candidate injector type for closed-spaced direct injection (DI) gasoline engines. In such a system, the spark plug must be located close to the spray and, during stratified operation, the spray is ignited very soon after the fuel droplets have been vaporized. Thus there are very high demands on the sprays used in such a system. An additional challenge is the positioning of the spark plug relative to the spray; both consistent ignitability and the absence of liquid fuel droplets must be achieved. Many injector parameters influence spray formation; for example, hole diameter, length to hole diameter ratio, nozzle hole configuration etc. This paper investigates the spray formation and spray induced air movement associated with rotational symmetrical and asymmetrical nozzle hole configurations. Four different nozzles with different hole configurations and umbrella angle were investigated both experimentally and numerically in a heated/pressurized spray chamber. Their influence on spray formation, spray induced air motion, cross-flow velocity, fuel/air ratio, turbulence and cycle-to-cycle variations were studied. It was found that rotational symmetrical configurations produce non-coherent isolated clouds of fuel. If an asymmetrical configuration is used instead (holes positioned along a horseshoe-shaped arc) then, by choosing the injector configuration carefully, it is easier to obtain a coherent fuel cloud; this also facilitates better control over the conditions at the spark plug, for example the fuel/air ratio, cross-flow velocity and turbulence. Furthermore, asymmetrical nozzles benefit from smaller fuel gradients and enhanced mixing between spray plumes as a result of shorter spray plume distance and improved spray-induced air motion. All the nozzles tested produced partially premixed vapor clouds, with cycle-to-cycle variations. These variations may be an important issue for ignition stability in a closed-spaced combustion system.
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.001 |
| 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.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".