Studio hour·45 minutes

Studio Hour: Gradient Parity Check

Compare an analytical gradient with a finite-difference estimate before trusting a training loop.

Scenario

Loss is changing, but a sign or scaling error may still make the update mathematically wrong.

You will demonstrate

  • Calculate a centered finite difference.
  • Measure relative error.
  • Write a regression tolerance.

Project evidence

Show the work, not a checked box.

Each response is stored in this browser as you type. Include metrics, test output, or a decision rationale wherever the deliverable asks for it.

1

Publish the parity check

Record the scalar function, analytical gradient, numerical gradient, epsilon, relative error, tolerance, and result for one normal and one boundary case.

Required evidence: A two-row parity table plus the exact assertion used in the regression test.

0/80 minimum characters

Runnable Python lab

Measure gradient agreement

Implement a centered finite difference for a tiny scalar loss.

Project defense

Why use a centered finite difference?

Rubric self-review

Rate the evidence, not your effort: 0 missing, 1 weak, 2 adequate, 3 strong. All criteria must be reviewed, but a low honest score does not get hidden.

The check states epsilon and tolerance, compares independent calculations, and includes a boundary case.

Useful references

Project completion gate

Completion is controlled by stored evidence, deterministic tests, a decision defense, rubric review, and the artifact when required.

Evidence pendingCode pendingDefense pendingRubric pending

Optional cloud portfolio

Submit evidence across devices.

An account is required. Submit only when the local completion gate passes. AI review is advisory and separate from deterministic completion.

Account settings