Courses / Physics and engineering / Model, constrain, control and troubleshoot / Defend a design and troubleshoot its failure Build and defend your work Defend a design and troubleshoot its failure Choose a virtual motion, power or heating design and specify a target plus a binding constraint. Compare alternatives, deliberately introduce a failure or disturbance, and justify a diagnostic or control change using captures from at least two experiments. This is a model-based design review, not authorization to operate physical hardware.
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 Choose the kind of work you want to produce School investigation College investigation Workplace application Create a virtual-device design poster with a labeled input-to-output diagram, units, two candidate settings and one failure case. Use a motion or energy experiment plus the controller or circuit-diagnosis experiment to explain why a good default can fail.
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 Target, constraints and units Define the required output, a hard limit and the scenario. Label dimensions and distinguish a preferred objective from a mandatory constraint.
Mechanism and checks Explain the model from inputs through intermediate quantities to output. Check a known numerical case and a physical accounting identity where applicable.
Feasible alternatives Compare at least two captured settings with the same assumptions. Reject an infeasible setting even if its target error or useful power looks better.
Failure and diagnosis Introduce delay, bias, loss or disturbance. State competing causes and the next measurement that would distinguish them; do not merely name the revealed fault selector.
Recommendation and validation boundary Choose a design or control change, show a stress case, and list unmodeled effects and empirical measurements needed before deployment.
Your artifact: code, analysis, prototype or decision brief 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.
Load a text artifact Review your work against the rubric Targets, hard constraints and units are explicit. The mechanism and one independent arithmetic or conservation check are correct. Alternatives are compared under equal assumptions and feasibility is checked first. Diagnosis considers more than one explanation and measurement error. The recommendation distinguishes a bounded virtual result from validated physical performance. 13 evidence requirements remain Capture evidence from stopping distance. Capture evidence from trajectory constraints. Capture evidence from power and internal loss. Capture evidence from heat capacity and loss. Capture evidence from diagnose a circuit. Capture evidence from feedback and delay. Include two different input configurations from the same experiment to compare. Write your target, constraints and units. Write your mechanism and checks. Write your feasible alternatives. Write your failure and diagnosis. Write your recommendation and validation boundary. Add your project artifact: code, analysis, prototype or decision brief. Record my report Download report and evidence 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 engineering-project-motion Open case engineering-project-motion Case engineering-project-energy Open case engineering-project-energy Case engineering-project-control Open case engineering-project-control
Return to the course · My Work and backups
