Case study on a fire within a road‐based portable bitumen storage tanker
Bibliographic record
Abstract
The roofing industry makes use of bitumen to build and repair roofs of residential and commercial structures. It is therefore necessary to transport the material over roadways and into residential and light commercial areas within cities. This is oftentimes accomplished by hauling the material behind trucks in large tankers that often have capacities of a few thousand gal. The material is flammable however and emits toxic and flammable off‐gases as it ages. As such, the storage, handling, transportation, and use of this material is inherently hazardous and these road portable tankers present a hazard not only to the companies and employees that use them, but also to the communities and businesses the companies serve. This article examines the events leading up to a fire that began within one such towed bitumen storage tanker used by a roofing company in Montreal in 2009. The incident is reviewed along with the hazards posed by these tankers. Conclusions are presented with regard to the causation of the fire based on the design of the tanker and available information. The learnings from this incident may prove helpful to other businesses that process, store, and use high molecular weight, sulfur‐containing hydrocarbon mixtures. © 2019 American Institute of Chemical Engineers Process Saf Prog: e12038 2019
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.006 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.004 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".