Teacher material · Page · Unpublished in Canvas

Facilitator Guide: Picture This Day 4 — Train It + Connect It

Canvas state
Unpublished

TEACHER ONLY · LESSON GUIDE

Picture This Day 4 — Train It + Connect It

Use this page to run the lesson. The student item directly below remains the independent and absence route.

Daily Learning Contract

Topic: Model design and coded response

Objective: Students will apply an iterative design process to train distinct classes, test reliability across users and conditions, and revise the model or coded response from evidence.

TEKS:
  • §126.19(c)(3)(B) — discuss and implement a design process that includes planning, selecting digital tools to develop, test, and evaluate design limitations, and refining a prototype or model; and
  • §126.19(c)(2)(C) — modify and implement previously written code to develop improved programs.

Demonstration of learning: Planning sheet, shareable model URL, one working coded response, partner-test evidence, and a named reliability improvement.

Before class

Time: One class period

Student route:
Day 4 · Train It + Connect It

Use what already exists: Day 4 deck; planning sheet DOCX/PDF; Teachable Machine; RAISE Playground template.

Lesson flow

  1. Launch: Contrast a model prediction with the code that decides a response.
  2. Model: Model exact class-name matching and one visible working action.
  3. Do: Pairs plan, train, partner-test, export, and connect their model.
  4. Check + support: Check for varied examples and one working response; use a checklist and driver/tester roles.
  5. Close + handoff: Collect planning evidence/model URL and preserve the project for remix.

Check before students leave

Ask each student or team to point to the specific evidence named above and explain one choice, test, or revision. Completion alone is not evidence of understanding.

Support + troubleshooting

Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.

When stuck: Ask students to show the exact step where the system stopped, then check setup, inputs, and saved work before replacing the task.