Bibliographic record
Abstract
Pakistan started its nuclear power program by installing a 137 MWe Canadian Deuterium Reactor (CANDU) at Karachi in 1971 which became operational in 1972. The post-contract technical support for the Karachi Nuclear Power Plant (KANUPP) was withdrawn by Canada in 1976 as a consequence of Indian nuclear device test in 1974. Inspite of various difficulties PAEC resolved to continue to operate KANUPP and started a process for the indigenous fabrication of spare parts and nuclear fuel. The first fuel bundle fabricated in Pakistan was loaded in the core in 1980. Since then KANUPP has been operating on the indigenously fabricated fuel. The plant computer systems and the most critical instrumentation and Control systems were also replaced with up-to date technology. In 2002 KANUPP completed its original design life of 30 year. A program for the life extension of the plant had already been started. The second nuclear power plant of 300 MWe pressurized water reactor purchased from China was installed at Chasma in 1997, which started commercial operations in 2001. Another unit of 300 MWe will be installed at Chashma in near future. These nuclear power plants have been operating under IAEA safeguards agreements. PAEC through the long-term performance of the two power plants has demonstrated its competence to safely and successfully operate and maintain nuclear power plants. Pakistan foresees an increasingly important and significant share of nuclear power in the energy sector. The Government has recently allocated a share of 8000 MW for nuclear energy in the total energy scenario of Pakistan by the year 2025.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.005 | 0.001 |
| Scholarly communication | 0.004 | 0.001 |
| Open science | 0.000 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.123 | 0.035 |
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".