Prototypes, Testing and Evidence

Saying our intake got better is a claim. Showing a photo of version 1 and version 3, a table of test results and a sentence explaining what changed is evidence. This lesson is about collecting that evidence as you work, so the portfolio almost writes itself.

Prototypes and version history

• Give every version a clear name: V1, V2, V3. Write the date and a one-line summary of what changed.
• Take a before photo before you modify anything, and an after photo once it works.
• Photograph from the same angle each time so changes are easy to compare.
• Record why you changed it, linking to the test result that caused the change.

Testing with real numbers

1. 1
   Ask one question

   For example: how long does the lift take to reach the top position?
2. 2
   Fix the setup

   Use the same battery charge level, field position and procedure every time so results are comparable.
3. 3
   Repeat trials

   Run at least 5 to 10 trials. One trial can be luck; many trials show a pattern.
4. 4
   Record immediately

   Write each result in a table as it happens, including failures.
5. 5
   Analyse

   Calculate an average or success rate and compare it with your goal.

Charts help judges see a pattern quickly. Use a bar chart to compare versions or options, and a line chart to show change over time or over a range, such as power level. Label both axes with units, give the chart a title, and keep one main message per chart.

Close the loop: what changed?

Every test section should end with one sentence that starts with something like Because of this result, we.... Without it, data is just numbers. With it, the data becomes part of your engineering story and leads to the next version.

Evidence that explains itself

• Photos: crop to the important part, and add arrows or labels if needed.
• CAD screenshots: show the relevant view, hide unrelated parts, and include key dimensions.
• Code snippets: show only the few lines that matter, not whole files.
• Captions: every image needs one that says what it shows and why it matters.

1package org.firstinspires.ftc.teamcode;
2
3import com.qualcomm.robotcore.eventloop.opmode.LinearOpMode;
4import com.qualcomm.robotcore.eventloop.opmode.TeleOp;
5import com.qualcomm.robotcore.hardware.DcMotor;
6import com.qualcomm.robotcore.util.ElapsedTime;
7
8@TeleOp(name = "Lift Timing Test")
9public class LiftTimingTest extends LinearOpMode {
10    @Override
11    public void runOpMode() {
12        DcMotor lift = hardwareMap.get(DcMotor.class, "lift");
13        lift.setMode(DcMotor.RunMode.STOP_AND_RESET_ENCODER);
14        lift.setTargetPosition(1200); // top position in encoder ticks
15        lift.setMode(DcMotor.RunMode.RUN_TO_POSITION);
16        ElapsedTime timer = new ElapsedTime();
17
18        waitForStart();
19        timer.reset();
20        lift.setPower(0.8);
21
22        while (opModeIsActive() && lift.isBusy()) {
23            telemetry.addData("Position", lift.getCurrentPosition());
24            telemetry.update();
25        }
26        double seconds = timer.seconds();
27        lift.setPower(0);
28
29        while (opModeIsActive()) {
30            telemetry.addData("Time to top (s)", "%.2f", seconds);
31            telemetry.update();
32        }
33    }
34}