Annual Hanford Seismic Report for Fiscal Year 2004
Bibliographic record
Abstract
The Hanford Seismic Assessment Program provides an uninterrupted collection of high-quality raw and processed seismic data from the Hanford Seismic Network for the U.S. Department of Energy and its contractors.The Hanford Seismic Assessment Team locates and identifies sources of seismic activity and monitors changes in the historical pattern of seismic activity at the Hanford Site.The data are compiled, archived, and published for use by the Hanford Site for waste management, Natural Phenomena Hazards assessments, and engineering design and construction.In addition, the seismic monitoring organization works with the Hanford Site Emergency Services Organization to provide assistance in the event of a significant earthquake on the Hanford Site.The Hanford Seismic Network and the Eastern Washington Regional Network consist of 41 individual sensor sites and 15 radio relay sites maintained by the Hanford Seismic Assessment Team.For the Hanford Seismic Network, there were 1,629 triggers during fiscal year 2004 of which 63 were local earthquakes.The largest earthquake was a magnitude 2.8 on February 28, 2004.This event occurred in the basalt on the south slope of the Horse Heaven Hills anticline near Wallula Gap.Stratigraphically, 25 earthquakes occurred in the Columbia River basalt (approximately 0-5 km), 20 earthquakes were in the pre-basalt sediments (approximately 5-10 km), and 18 earthquakes were in the crystalline basement (approximately 10-25 km).Geographically, 34 earthquakes occurred in swarm areas, 8 earthquakes were on major geologic structures, and 21 earthquakes were classified as random events.Fourth quarter earthquakes are reported in the annual report.For the Hanford Seismic Network, there were 554 triggers during the fourth quarter, of which 31 were earthquakes.The largest earthquake during the fourth quarter was a magnitude 1.4 event on August 17, 2004; this event occurred in the Horse Heaven Hills earthquake swarm area and was located in the pre-basalt sediments.Stratigraphically, a total of 14 earthquakes occurred in the Columbia River basalt (approximately 0-5 km), 13 earthquakes were in the pre-basalt sediments (approximately 5-10 km), and 4 earthquakes were in the crystalline basement (approximately 10-25 km).Geographically, 17 earthquakes occurred in swarm areas, 7 earthquakes were on major geologic structures, and 7 earthquakes were classified as random events.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.145 | 0.082 |
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".