Bibliographic record
Abstract
In many conflicts, the consequences of engineering projects are among the problems at issue, and engineers are unavoidably parties to the problems. Engineers need to raise their awareness of the potential effects of their projects, especially in situations of serious social and political contention, and to explore alternative designs or engineering solutions, and methods of implementation, that may ameliorate rather than exacerbate tensions. Engineers will also need to dialogue effectively with the many stakeholders affected if these projects are to be politically viable and achieve their technical purposes. The paper draws on several case studies of engineering projects in conflict situations, especially in developing countries. The article offers a check list of factors to take into account when designing and locating power, irrigation, mining, transport, and other types of engineering projects, in areas of conflict or potential conflict. The focus of the paper is primarily, but not entirely, on social conflict.
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.018 | 0.020 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.024 | 0.045 |
| Scholarly communication | 0.018 | 0.016 |
| Open science | 0.002 | 0.019 |
| Research integrity | 0.004 | 0.006 |
| Insufficient payload (model declined to judge) | 0.011 | 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".