Physical Transformation AtlasPTA
Source · source:schneider-2017-monroe-hydro-doe · report

Development of a project on North Unit Irrigation District's Main Canal at the Monroe Drop, using a novel low-head hydropower technology called the SLH100

Abraham Schneider, Gia Schneider, Katherine McKinstry, Meghan Harwood2017Natel Energy final report to the U.S. Department of Energy, award DE-EE0005420 (FOA DE-FOA-0000486, Advanced Hydropower Development); OSTI 1346739doi:10.2172/1346739

Atlas use: this report is cited as evidence by 0 claims and 1 named pathway. Not yet checked against Crossref.

Read in full (loop-3 pass 44; osti.gov timed out from this machine, so the Internet Archive's copy of the OSTI PDF, captured 04/02/2025, was read). One SLH100 hydroEngine (linearly moving foils rather than a rotor) commissioned September 2015 at an existing drop on the NUID main canal, Madras, Oregon: 'The nameplate capacity of the SLH100 at the Monroe Hydro Project is 250 kW. The gross head ranges between 4.1 meters and 5.1 meters. The machine can pass a maximum flow of 331 cfs. The SLH100 hydroEngine has run at maximum power of 267 kW with water-to-wire plant efficiency of 60% (73% hydraulic efficiency), meeting design expectations.' The report gives no formula for either efficiency and does not state the grid-side boundary; expected annual generation 873 MWh, 40 % annual capacity factor (80 % over the irrigation season).

Exploreclaims citing it · pathways citing it · cite

Claims citing this source · 0

No claim cites this source.

Named pathways citing this source · 1

Cite this source

Physical Transformation Atlas (2026). source source:schneider-2017-monroe-hydro-doe: Development of a project on North Unit Irrigation District's Main Canal at the Monroe Drop, using a novel low-head hydropower technology called the SLH100. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/schneider-2017-monroe-hydro-doe

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.