Flagship · Taiwan Polar Institute · open source
Python · PyPI · MCP · Pyodide / WASM
AquaScope
The open-source platform behind my commissioned work at the Taiwan Polar
Institute: water data, hydrology, and agricultural water management in one package.
37 unified data sources (USGS, Brazil ANA, Australia BOM, FAO, GEMStat, EU WFD
and more), Bulletin 17C flood frequency, FAO-56 crop water, baseflow separation, and an
agentic AI engine that scores 26 research methodologies, checks every step
against a method-precondition registry, and auto-executes the pipeline. On top of that sits
Studio, a seven-role research crew that takes a problem in plain language and
returns a finished deliverable bundle. CAMELS-validated, released on PyPI and citable by DOI.
- 2,200+ PyPI downloads and 25+ outside contributors, maintained solo
- An open archive of 67,000+ public gauges across ten countries, harvested weekly and published as GeoParquet
- 37 REST API collectors normalize every upstream source into one schema, so downstream analysis is source-agnostic
- Zero-install Explorer: the same Python runs client-side in the browser (Pyodide · DuckDB-WASM · MapLibre), no server at all, and its Ask panel can run on an on-device model (Chrome's built-in Prompt API or WebLLM) with no API key
- Studio: one plain-language problem and a coordinate run a seven-role crew (consultant, scout, methodologist, analysts, interpreter, critic, author) over a single shared workspace, returning a Word report, an Excel workbook, figures and a runnable notebook. The plan is shown and approved before anything executes, a failed gate fails its step rather than the study, and every finding is graded and points at the result it rests on. My own state-machine orchestrator, not a framework wrapper
- MCP server exposing 30+ tools to Claude Desktop / Claude Code / Cursor, seven of them driving Studio, alongside a 25+ command CLI
- HydroGym: a benchmark that scores hydrology agents on real sites, pitting the gated planner against baseline agents (including a plain tool-calling loop) on task outcome, plan quality against hand-written expert plans, and the finished report, with a published leaderboard and per-task cost accounting
- Maintained in the open: issue triage, PR review, versioned releases, CI with a nightly CAMELS benchmark run, Zenodo DOI