Cloud Computing Basics

Short pre-workshop handout for fellows

   
Purpose Give everyone common vocabulary for using cloud tools during the workshop.
Required video Watch: Cloud Computing Explained
Scope This is only a cloud-computing primer. The survey paper and forecasting research are separate topics.

Before the workshop

  • Watch the video above and note any unfamiliar terms.
  • Bring a laptop, charger, and browser access.
  • Have a GitHub account ready, if workshop materials will be shared there.
  • Use only sample, public, or anonymized data in shared demos.

What “cloud” means here

Cloud computing means using remote computers, storage, and software over the internet. For hydropower work, think of it as a shared analysis workspace — useful for data processing, collaboration, and reproducible notebooks — not a replacement for plant-control systems.

Five ideas to know

Concept Plain meaning for engineers
Compute Rented machines for scripts, simulations, data cleaning, and batch jobs.
Storage A shared place for data files, reports, models, logs, and figures.
Notebook An interactive document combining code, explanation, plots, and results.
API A standard way for software tools to exchange data.
Access control Rules for who can read, edit, download, or delete files and code.

Hydropower examples and safety boundaries

Useful cloud examples Do not upload without approval
- Anonymized flow, rainfall, reservoir-level, or efficiency data
- Batch calculations that are slow on a laptop
- Shared notebooks, figures, dashboards, and workshop code
- Versioned scripts and reproducible analysis folders		 - SCADA/PLC commands or operational network details
- Credentials, tokens, SSH keys, or passwords
- Confidential plant drawings, security-sensitive files, or restricted data
- Raw personal or proprietary data without review

By the start of the workshop, participants should be able to…

  • Explain the difference between cloud compute, storage, notebooks, and APIs.
  • Recognize why GitHub and shared notebooks help collaboration.
  • Identify which hydropower data can be safely used in a demo and which cannot.