A technical view on Pakistan's nuclear weapons programme
Bibliographic record
Abstract
Pakistan performed at least two nuclear weapons tests in 1998 as a direct response to the Indian nuclear tests earlier the same year. With this act, Pakistan became the seventh country to successfully complete a nuclear weapons programme. The Pakistani nuclear weapons arsenal consists of both uranium and plutonium weapons and the country has an extensive nuclear industry with all facilities necessary for enrichment of uranium, production of plutonium and reprocessing of spent reactor fuel. Pakistan acquired a Canadian civil heavy water nuclear reactor in 1971; KANUPP-1. In 1976 however, the cooperation with Canada ended as Canada stopped supplying fuel for the reactor. At this point, Pakistan had acquired know-how and experience to manufacture its own fuel and also started building an independent nuclear industry with several unsafeguarded reactors at the Khushab site. With French assistance, a reprocessing plant was constructed and consequently, Pakistan is today in possession of all components necessary for developing and employing both uranium and plutonium nuclear devices. In this presentation, we will explore technical challenges associated with bringing a country such as Pakistan under the existing or proposed treaty verification following treaties such as the NPT, TPNW and FMCT. Using a simulation framework and estimates based on known physical quantities and derived abilities, we will discuss what conclusions can be drawn with regards to uranium and plutonium stockpiles.
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.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.005 | 0.003 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.025 | 0.005 |
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".