Bibliographic record
Abstract
Among the letters delivered to the office of the president and general manager of Cominco in Trail, British Columbia on a snowy February 26, 1941, was one of special significance. Although stamped secret, the letter seemed innocent enough. It carried a request from the National Research Council of Canada for information on the type of cell used by Cominco in their electrolysis of water process and for information on Cominco's ability to make heavy water. This innocent-sounding note was to launch the company into one of the most remarkable projects of its long history, involvement in the Manhattan Project, the giant engineering undertaking which was to bring forth, in the summer of 1945, the atomic bomb. Nearly two years later, the company would sign contracts with the United States Government to produce a substance called heavy water, but not before some careful bargaining had been conducted on both sides. As early as 1934, Cominco had investigated the properties of heavy water, and had corresponded with the National Research Council on the subject. But these early investigations did not go far. It took the outbreak of hostilities in Europe in 1939 to focus attention on heavy water because of the research that was hurriedly being conducted into atomic fission. It will be necessary here to explain briefly atomic fission, and the relationship of heavy water to the process. A nucleus, which is the heart of the uranium atom, fissions, or splits apart, giving off particles called neutrons. These particles leave the nucleus at enormous speeds. For a chain reaction to develop the speed of the neutrons must be moderated so that they can come into contact with other uranium nuclei. And every
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.016 | 0.005 |
| Scholarly communication | 0.010 | 0.003 |
| Open science | 0.002 | 0.006 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.052 | 0.009 |
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".