Alkali silika reaksiyon genleşmesinin betonun mekanik özelliklerine etkisi.
Bibliographic record
Abstract
Alkali-silica reaction (ASR) is a chemical deterioration process which arises in concrete due to reactive aggregate from its constituent, sufficient alkalis from cement or external resources and humidity about 85%. ASR gel, formed by the reaction, absorbs water and expands so that it causes expansion and cracking in concrete. ASR has detrimental effects on mechanical properties of concrete. Therefore, ASR which is a long and a constantly progressive reaction may become a threat to the safety of concrete structures. This experimental study focuses on two main subjects. The first one is the effect of ASR on mechanical properties of concrete, which are compressive strength, flexural strength, splitting tensile strength, modulus of elasticity and pullout strength at expansion of over 0.04 % and the second one is the impact of the type of specimen on ASR expansion, which differs as prism, cube, and cylinder. Concrete specimens in different types for tests include not only fine river sand, a reactive aggregate, but also coarse limestone, a non-reactive aggregate. As known, some standards like ASTM C1293 and Canadian CSA–A23.2-14A, describe aggregates causing expansion more than 0.04% in concrete within 1 year as potentially deleteriously reactive. Firstly, immediately after the expansion of the specimens, exposed to ASR exceeded 0.04%, the mechanical tests were performed on both them and the control specimens. Secondly, the specimens, exposed to ASR for longer time, were tested at expansion of over 0.10% to investigate ASR effect on mechanical properties. The investigation results confirm that expansion of over 0.04% in concrete from ASR caused losses in mechanical properties of concrete at different rates. With higher expansion, losses increase significantly especially in flexural strength and pullout strength of concrete. Moreover, higher rate of expansion in prisms than cubes at any time and cylinders proves that the type of specimen has an important role on rate of ASR expansion according to results.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.011 | 0.005 |
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".