← ClaudeAtlas

rseng-green-computinglisted

Covers the environmental footprint of research computing: measuring and reporting energy use and carbon emissions of computations (CodeCarbon), reducing them through efficient code, right-sized hardware and carbon-aware scheduling (CATS), the GREENER principles and the Software Carbon Intensity metric. Use when the user asks about the carbon or energy cost of their computations, wants to make workloads greener, mentions sustainability of computing, CodeCarbon, CATS or the Software Carbon Intensity metric. Use PROACTIVELY when planning large training runs, simulations or parameter sweeps - footprint measurement is worthless retrospectively. (Keeping the software project itself alive is rseng-maintenance-sustainability; making code faster is rseng-performance-profiling.)
fdiblen/rseng-agent-skills · ★ 20 · AI & Automation · score 81
Install: claude install-skill fdiblen/rseng-agent-skills
# Environmentally sustainable research computing Research computing has a real carbon footprint - large simulations, ML training runs and always-on services consume energy at a scale funders and institutions increasingly ask about. The GREENER principles for computational science frame the practice: Governance, Responsibility, Estimation, Energy and embodied impacts, New collaborations, Education and Research. For an agent the working core is: measure first, reduce second, schedule smart, report honestly. ## Measure before optimizing Never guess at footprint - estimate it: - CodeCarbon instruments Python code with a few lines (or a CLI wrapper) and estimates energy plus location-adjusted CO2e; add it to representative runs, not every run. - For non-Python or cluster workloads, estimate from job accounting (CPU/GPU hours x hardware power draw x facility PUE x grid carbon intensity) and state the assumptions. - Record estimates alongside results the same way runtimes are recorded, so the cost of a paper's computations is reportable. The Software Carbon Intensity (SCI) specification (an ISO standard) gives a defensible formula when a formal number is needed: operational plus embodied emissions per functional unit. ## Reduce Order interventions by leverage, and quantify the win when possible: 1. Compute less: cache intermediate results, avoid re-running unchanged pipeline stages (rseng-workflows), kill zombie jobs, right-size parameter sweeps before launch