MétaCan
Menu
Back to cohort

Iron Oxide Coated Sand for Arsenic Removal: Investigation of Coating Parameters Using Factorial Design Approach

2006· article· en· W2157867843 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenuePractice Periodical of Hazardous Toxic and Radioactive Waste Management · 2006
Typearticle
Languageen
FieldEnvironmental Science
TopicArsenic contamination and mitigation
Canadian institutionsUniversity of Regina
FundersNatural Sciences and Engineering Research Council of CanadaU.S. Environmental Protection Agency
KeywordsArsenicAdsorptionFactorial experimentFractional factorial designCoatingIron oxideFiltration (mathematics)ChemistryOxideWater treatmentChemical engineeringInorganic chemistryMetallurgyEnvironmental chemistryMaterials scienceEnvironmental engineeringEnvironmental scienceMathematicsOrganic chemistry

Abstract

fetched live from OpenAlex

Iron oxide-coated sand filtration is reported as one of the most viable technological options for arsenic removal from drinking water by the United States Environmental Protection Agency. For substantial utilization of the adsorption properties of iron oxide-coated sand for arsenic removal, it is important to understand the factors contributing to its adsorption capabilities. The effects of seven factors i.e., coating pH, temperature, iron concentration, number of coatings, aging, pH of the solution and mass of the adsorbent on arsenic (V) and arsenic (III) removal were investigated. Two sets of 27-4 fractional factorial design were adopted to identify the significant factors in the arsenic adsorption process. The results showed that coating pH, temperature, and solution pH had the most significant influence on As(V) removal and coating pH, temperature, solution pH and mass of adsorbent had the greatest effect on As(III) removal. The effects of other factors were relatively small on arsenic removal.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.542
Threshold uncertainty score0.651

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.025
GPT teacher head0.251
Teacher spread0.226 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it