High-Velocity Impact Comminution of Magnetite
Bibliographic record
Abstract
Conventional comminution (crushing and grinding) uses compressive forces to initiate and propagate cracks throughout the rock mass, yet the material actually breaks under tension since this strength characteristic is about 10 percent of the compressive strength. Converting a compressive force into a tensile one is inefficient - of the order of 1 to 2 percent. On the other hand, blasting shows energy efficiencies of the order of 10 to 20%. Part of this difference is due to forces being applied directly in tension (from the inside-out), but also because the velocity of impact is orders of magnitude higher (10,000 m·s -1 versus 10 m·s -1 ), i.e., the rate of energy input is very high (micro-seconds vs. seconds in conventional comminution). This paper reports on studies that show how the energy efficiency of comminution can be enhanced by high-velocity impact. This research project has carried out investigations into the relationship between energy efficiency with energy input level and impact velocity during rock fragmentation by metal projectiles. The project has also examined rock-on-rock breakage. Samples of magnetite particles of varying weights and size distributions were impacted by a projectile at velocities from 50 m·s -1 to 400 m·s -1 . The specific surface area of the sample was measured before and after each experiment, and the energy recovered as new surface energy (energy efficiency) was calculated. The results indicate that energy efficiency increases to about 5% as impact velocity enters the range from 200 to 300 m·s -1 . This efficiency is over 3 times that observed in conventional comminution. Above this velocity, the efficiency begins to fall off although significant comminution at higher than normal efficiencies are still attained. The improvement results from both increased rate of energy input and increased impact velocity. Rock-on-rock impacts using a glass projectile shows that the energy of new surface generation is distributed between the projectile and the sample to a combined level similar to that of the steel-on-rock tests in which all the useful energy is retained within the sample. Suggestions are given as to how this energy improvement could be scaled-up into an impact crusher.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 teacher head, 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".