Learn

Learning preferences

Make learning more comfortable. Changes apply immediately.

Enlarges page content, including diagrams and their labels. You can also use your browser’s zoom.

Choose the colours that are easiest for you to distinguish. Applies to lesson diagrams and lab plots. Labels, shapes, hatching and line patterns also distinguish meanings. Source photographs and raw image brightness stay unchanged; mask-only views are available for image overlays.

ExampleComparisonSample link

Saved in this browser on this device. Preferences are separate from progress backups.

SCIENCE · INVESTIGATE AND EXPLAIN

Defend a water decision with trade-offs

Compare indicators and revise a recommendation after a supplied demand stress.

Learning outcome: Distinguish physical consequences from priorities and specify monitoring that could change a decision.

Starting recap

A balanced water budget does not establish ecological adequacy or a uniquely best allocation.

All lessons are open directly. Your saved experiments remain when you leave and return.

Try

Regular release 10 leaves 30/140, about 21.4 percent, of requested service unmet.

Open the experiment

Predict

Can one policy improve controlled release while worsening service?

Experiment

Build a matched comparison table, add a demand stress and write a bounded intervention brief.

Allocate a bounded reservoir under stress

Fictional water-allocation policy · separate observed river record · Original fictional reservoir, capacity 100 m³ and initial storage 40 m³. Each daily bin receives all its supplied inflow, spills above capacity, prioritizes the requested downstream release, then supplies service demand from remaining water. No evaporation, groundwater, within-day hydraulics or forecast. Release targets are policy assumptions, not ecological adequacy thresholds. Unmet requests are not water fluxes. This model is not calibrated to the separate USGS river record.

Reset keeps your prediction, captures and practice history.

One reservoir, two requests and a fixed order

Regular inflow; service request 20 m³/day. This fictional store starts with 40 m³ and holds at most 100 m³. The requested controlled downstream release is 5 m³/day. The service request is 20 m³/day. These are supplied teaching conditions, not a real reservoir forecast or recommended ecological flow.

Predict before comparing: if you increase the release request under the same inflow scenario, what happens to service and storage? Treat your preferred allocation as a stated choice; the arithmetic does not decide whose needs should take priority.

  1. Receive the whole day's supplied inflow into the starting store.
  2. Spill any volume above 100 m³ before either requested allocation.
  3. Prioritize controlled downstream release, capped by the water available.
  4. Supply school/community service from the remaining water; retain the remainder for the next day.

This daily event order is a policy and timing assumption. It does not resolve within-day hydraulics. Changing the order could change spill or service. Evaporation, groundwater exchange and other losses are omitted.

Stored volume (m³): initial state and end-of-day snapshots020406080100Capacity 100 m³01234567Day 0 is initial storage; days 1–7 are after allocationLines guide the eye between snapshots; they are not within-day flow predictions.

Close the water ledger

Across seven days: 40 initial + 140 inflow = 0 spill + 35 controlled release + 140 service supplied + 5 final storage, all in m³. Balance residual: 0 m³.

Spill and controlled release both leave the store, but their timing and consequences need not be equivalent. More released water is not, by itself, evidence that ecological needs are met. Unmet requests are comparisons against a target, not additional water leaving the store.

Event order left to right; every quantity is m³ within the stated daily bin
DayStartInflowBefore spillSpillAfter spillControlled releaseAfter releaseService suppliedEndBalance residual
140206006055520350
235205505555020300
330205005054520250
425204504554020200
520204004053520150
615203503553020100
71020300305252050

Keep requests visible when water runs short

All volumes in m³; actual fulfillment plus shortfall equals the request
DayRelease requestedRelease actualRelease shortfallService requestedService suppliedUnmet service
155020200
255020200
355020200
455020200
555020200
655020200
755020200
Seven-day totals353501401400
Check a matched comparison and a timing counterexample

Worked comparison, separate from the current selection: under regular inflow, requesting 5 m³/day releases 35 m³, supplies all 140 m³ of service and leaves 5 m³. Requesting 10 m³/day releases 70 m³, supplies 110 m³ of service and leaves zero; unmet service rises to 30 m³. One reported indicator improves while another worsens. Choosing between these cases needs objectives and evidence beyond this ledger.

For the pulse case, day one begins with 40 m³ and receives 80 m³. The resulting 120 m³ exceeds capacity, so 20 m³ spills before allocations. Supplying service first would be a different timing model. Do not interpret the daily snapshot line as evidence that this pulse arrives gradually.

Transfer: keep the requested release at 5 m³/day and compare regular inflow with dry stress, then with higher service demand. Identify which input changed, show the complete water balance, and state one additional observation needed before proposing a real intervention. The separate USGS streamflow record is an observation audit; it does not calibrate these inputs or establish permitted withdrawals.

Final storage 5 m³; service supplied 140 of 140 m³ requested; unmet service 0 m³.

40 + 140 inflow = 0 spill + 35 controlled release + 140 service + 5 storage (m³). Requested controlled release 35 m³; release shortfall 0 m³. Priority and daily event order are assumptions, not a claim about the best policy.

Captures preserve recipes and replay their calculated results. They are synthetic model evidence, not physical measurements.

Understand

Separate a physical comparison from a recommendation

A recommendation needs both evidence and a stated objective. The reservoir investigation can calculate supplied service, controlled release, spill and storage under its assumptions. It cannot decide whose needs should take priority or translate every extra cubic meter into ecological benefit. Begin your brief by identifying the decision, affected groups and indicators before choosing a preferred setting.

Use regular inflow for your first matched comparison. Predict what changes when requested release rises from 5 to 10 m³/day. Capture both recipes and retain the same initial storage, capacity, service demand, seven-day interval and daily allocation order. This pairing isolates the changed request within the model; it does not represent an independently observed policy intervention.

Build a decision table without a hidden score

With request 5, controlled release totals 35 m³, service is 140, unmet service is zero and final storage is 5. With request 10, controlled release totals 70, service is 110, unmet service is 30 and final storage is zero. Neither has spill. Copy these indicators into separate columns rather than collapsing them into an unexplained sustainability score.

The second policy improves the indicator “volume of controlled release” while worsening “unmet service.” Whether that is preferable depends on objectives and consequences. A requirement for ecological timing, a service-access concern or a reserve requirement could alter the decision. None is supplied as a measured threshold here.

For a percentage refresher, 30 m³ unmet service out of 140 requested is 30/140 × 100, about 21.4%. The denominator is requested service, not initial storage or supplied service. Name the denominator in your report. A percentage without its reference quantity can conceal which need is being discussed.

Test your recommendation under a stress

Retain request 5 and switch to demand stress: regular inflow remains 20 m³/day but service demand becomes 30. Total requested service is 210. The model supplies 145, leaving 65 unmet, while release remains 35 and final storage is zero. Check 40 + 140 = 35 + 145.

Compare this result with the regular schedule. Increased demand does not generate new water. Some extra service comes from drawing down the remaining reserve, but the whole increase cannot be fulfilled. State whether your recommendation survives this stress and which outcome prompted any revision. Avoid claiming robustness to every drought or demand pattern from these four supplied scenarios.

The USGS groundwater-development discussion illustrates why a baseline water budget alone does not establish sustainable withdrawal. Here too, a balanced ledger is necessary accounting, not a complete environmental approval. Future monitoring would need actual inflows, withdrawals, return flows and relevant ecological or service outcomes.

Prepare a bounded intervention artifact

Write a short report with your original prediction, matched settings, numerical comparison, stress result, chosen priority and a condition that would change your recommendation. Include a sketch or table whose units and time boundary a second reader can reconstruct. Preserve a plausible alternative: perhaps changing demand timing or measuring return flow could alter the problem, but those interventions are not simulated by the current controls.

Keep the fixed USGS streamflow record in a separate evidence paragraph. It demonstrates real variability and the interpretation of daily discharge statistics; it does not validate the reservoir capacity, establish available school water or supply a policy effectiveness estimate. This distinction makes the artifact more useful because another reader can see which claims follow from a model and which describe observations.

Transfer: explain a reversed priority

Two fictional plans have identical requested service of 100 m³. Plan A supplies 95 and releases 20; plan B supplies 85 and releases 35. No other consequences are supplied. Calculate unmet service for each, identify the trade-off, and explain what evidence is needed before recommending B. Do not invent ecological thresholds to settle the choice.

Check the water-tradeoffs transfer

Unmet service is 5 m³ for A and 15 for B. B has 15 m³ more release but 10 m³ more unmet service. More release is an improved volume indicator, not proven ecological adequacy. A recommendation needs explicit priorities and evidence about timing, users, downstream effects and other balance terms. Public worked feedback is practice, not independently reviewed policy competence.

Apply

A larger controlled-release total alone establishes:

Public practice checks a specific claim. It does not establish independent mastery.

Name the chosen priority, a worsened indicator, an alternative and needed real observations.

Continue

Completion requires a saved prediction, at least one capture and a reflection. Presence checks do not grade your reasoning.

Skipping retains experiments and awards no mastery.

Previous: Read actual daily streamflow evidenceNext: Measure the biodiversity claim
Save a science backup or import one

Science work is stored locally in this browser, separately from mathematics and AI. It does not sync automatically. Use this science-only backup; this checkout's older all-subject export does not include science.

A legacy file is available only when the complete snapshot fits the 36 MB limit. For larger snapshots, prepare a complete file set below; never discard notebooks to make a smaller file.

Matching imported notebook drafts replace their current drafts. Omitted lessons and known first attempts remain. Export your current work first if you want to retain both drafts.

Complete file sets and course backups

A file set can hold more work than one science file. Keep its manifest and every part together. Each file is limited to 36 MB. This format needs this version of LearnAI or a compatible newer version; older versions can use only the legacy single-file backup above.

The set includes every saved science course and global continuation at this moment. Later edits need a new export. A conflicting tab exports its own visible work, which may differ from saved work in another tab.

0 file(s) selected. File order and filenames do not determine identity. Missing, changed or conflicting parts block the entire restore; no good part is applied by itself.

Science storage: loading. No account or remote computation is required.