TRV-2026-1628Certified recordPeer-reviewed

Predicting multi-heavy-metal adsorption on bimetallic zeolitic imidazolate frameworks via interpretable machine learning: From latin hypercube design to web implementation

Efficient remediation of heavy metal-contaminated water requires systematic evaluation of adsorbent performance under complex environmental conditions. In this study, an interpretable machine learning approach was applied to predict multi-metal adsorption on bimetallic zeolitic imidazolate frameworks (ZIFs) and to analyze the contributions of material properties, aqueous chemistry, and metal ion characteristics. Three structurally distinct bimetallic ZIF-derived materials were synthesized and evaluated via adsor…

Climate · Good Space — documented gain · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

A grid-search-tuned neural network predicted heavy-metal adsorption capacity on three bimetallic ZIF materials with high accuracy and exposed which factors drive uptake, supporting more targeted adsorbent design.

What this doesn’t fix

On independent validation data the web platform had a mean absolute percentage error of 18 %, noticeably looser than the R2 of 0.98, and the data cover only three bimetallic ZIF-derived materials.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1628, v1: “Predicting multi-heavy-metal adsorption on bimetallic zeolitic imidazolate frameworks via interpretable machine learning: From latin hypercube design to web implementation.” Truvace, 2026-10-16. /record/TRV-2026-1628 (accessed at citation time). sha256 9ebb6088426d3ea6…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv19ebb6088426d…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1628 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.