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.

Build and defend your work

Model and audit a small linear system

Choose a resource, measurement or transformation scenario. Submit a matrix with units, an exact-system diagnosis, a least-squares comparison and an interpretation of a projection or eigen-direction. Keep exact equations, approximate fits and decisions separate.

Choose an audience, investigate alternatives, copy evidence from your experiments, and produce an artifact. You can open this project at any time. Reports, numerical transfer checks and human review are separate outcomes.

Your project workspace

Create a two-resource school-event model, draw its vectors and explain an inconsistent set of requested totals.

1. Collect and compare evidence

Required experiment sources:

Include every source above and at least one pair with different inputs from the same experiment. Explain confounding changes yourself; the presence check does not judge your interpretation.

Open an experiment and change an input or capture a trial to make evidence available here.

2. Write and revise your report

State the domain, units, target claim or objective and assumptions.

Include a diagram, calculation, proof or runnable algorithm; explain each important step.

Compare captured settings, preserve failed cases and distinguish observations from general arguments.

Apply your method to a different case and verify it independently by substitution, enumeration or a justified argument.

Explain when the method fails or changes and what further evidence is needed.

This field stores up to 12,000 characters of inert text. Code runs only through the explicit bounded editor in the relevant lessons; project attachments never execute.

Review your work against the rubric

  • Shapes, coordinates and units are explicit.
  • Solution count follows independent equations and consistency, not visual guessing.
  • Residuals and least-squares objective are correctly calculated.
  • Projection/eigenvector claims include assumptions and information loss.
  • A fresh case is checked independently; a fitted model is not a causal claim.
11 evidence requirements remain
  • Capture evidence from Build a point from directions.
  • Capture evidence from When do equations identify one point?.
  • Capture evidence from Fit a line when equations disagree.
  • Capture evidence from Find a direction a matrix preserves.
  • Include two different input configurations from the same experiment to compare.
  • Write your question, variables and assumptions.
  • Write your worked method and authored artifact.
  • Write your comparison and evidence.
  • Write your fresh case and verification.
  • Write your limitations and decision.
  • Add your project artifact: code, analysis, prototype or decision brief.

Editing the report or evidence returns it to draft. Recording verifies field presence and input comparisons, not correctness of your reasoning or code.

3. Check transfer to unfamiliar cases

These authored cases use different numbers or conditions from the lesson practice. They are public local checks, not secure certification. Each case permits three submissions. Opening, first responses and attempt counts survive imports; no reset creates fresh evidence.

Case matrix

Case solve

Case residual

Case eigen

Return to the course · My Work and backups