RAOP
Activities
RAOP activities are delivered through a structured simulation-to-hardware workflow grounded in Guided Inquiry-Based Learning (GIBL). During the two-week virtual phase, participants complete guided digital-twin labs and build intuition using starter MATLAB/Simulink models and curated concept reviews. During the one-week on-site phase, participants validate selected results on physical hardware in the AVRC Laboratory with step-by-step support from the program team. The overall objective is to produce robotics and automation learning experiences that are classroom-ready and feasible for adoption in high-need school districts (LEAs).
Common RAOP Workflow
Each platform strand follows the same program structure to support consistent learning evidence and reliable classroom translation.
RAOP activities use guided inquiry rather than “cookbook” instructions. Each lab starts with a guiding question and scaffolded steps. Participants run a baseline case, make small changes, and use evidence (data, plots, and observations) to explain what happened and why. This approach supports educators who are new to the topic while keeping the work concrete, doable, and ready for classroom transfer.
- Setup and orientation (software, access, and workflow expectations).
- Concept reviews tied to each lab (controls, modeling, sensing, autonomy).
- Guided digital-twin labs using starter models and structured procedures.
- Formative checks: short checkpoints, reflections, and feedback cycles.
- Draft classroom translation: lesson flow, student tasks, and assessment plan.
- Hardware demonstrations aligned to virtual lab objectives.
- Validation of selected simulation results and interpretation of discrepancies.
- Structured troubleshooting and discussion of measurement, noise, and constraints.
- Finalize classroom-ready deliverables with feasibility and pacing refinements.
- Documentation of requirements and adaptations suitable for high-need LEA contexts.
Participant Materials
Core materials used across RAOP are organized within the Academic Resources repository. These resources support the full workflow: setup, concept development, virtual labs, and on-site validation.
Before running RAOP labs, ensure your Windows development PC/laptop has the required software installed. Participants may use MATLAB/Simulink or Python workflows depending on the selected activities and cohort pathway.
- Simulink with Hardware: install MATLAB/Simulink and QUARC following installation instructions (distributed via RAOP website materials/portal).
- Simulink with Virtual Labs: install a MATLAB/Simulink version compatible with the Q Labs MATLAB Add-on, then install the add-on using MATLAB’s Add-on Manager.
- Python with Hardware: Python 3.11+ and the Quanser SDK for Windows.
- Python with Virtual Labs only: Python 3.11+, plus Q Labs and the Quanser SDK.
It is recommended to install the resources in a folder named Quanser under your Documents directory. This provides a stable local location for the materials and avoids issues that can occur when working from a temporary downloads folder.
- Install Git on your system.
- Open your Documents folder and open a Windows terminal in that folder.
- Run the command below to create a local folder named Quanser and clone the repository into it:
- Create a folder named Quanser under your Documents directory (example above).
- On the GitHub repository page, click Code → Download ZIP.
- Unzip the folder on your system.
- Open the unzipped folder (e.g., Quanser_Academic_Resources-main) and copy its contents into your Documents\Quanser folder.
- After installations and extraction steps are complete, restart your Windows PC/laptop.
- For the authoritative step-by-step instructions, refer to the Setting Up Your Computer section in the Quanser materials.
If you encounter a broken external installation link, use the Quanser Portal and the repository “Setup” section above as the authoritative source for current installation steps.
- RAOP provides cohort access to virtual lab environments used for simulation activities, complemented by on-site hardware sessions in the AVRC Laboratory.
- Participants will be added to the AVRC Lab Quanser Portal for access to platform instructions, training content, and technical support.
- Continued access beyond the cohort period may be available, subject to vendor licensing terms and program policies.
Expected Participant Outputs
Across all platform strands, participants complete a consistent set of outputs to support evidence of learning and classroom adoption.
- Virtual lab checkpoints (selected modules) with brief interpretation of results.
- Structured reflections or short lab notes documenting decisions, observations, and evidence.
- Draft lesson plan package (end of Week 2) aligned to a selected RAOP activity.
- Assessment artifacts: at least one formative check and one summative rubric aligned to objectives.
- Final classroom-ready implementation package (end of Week 3) including feasibility notes and adaptations.
Experiments and Groups
Each cohort includes eight educators divided into four groups (approximately two educators per group). Each group focuses on one platform strand. The RAOP team selects a subset of modules from the available library to fit the two-week virtual phase and the one-week on-site phase while maintaining alignment to program objectives and classroom feasibility.
Experiment 1 – Control Fundamentals (Qube-Servo 3) – Group 1A guided sequence covering instrumentation, modeling, analysis, and feedback control—first in virtual labs (digital twin), then reinforced through on-site hardware validation.
- The RAOP team selects a subset of modules to fit the two-week virtual phase and the one-week on-site phase.
- Selected modules use a consistent structure: concept review, application guide, lab procedure, and an assessment activity.
- Starter MATLAB/Simulink models are provided for simulation, identification, and controller tuning.
- Participants receive step-by-step coaching; prior MATLAB/Simulink experience is not required.
- Pipeline 0 – Instrumentation (e.g., hardware interfacing, filtering)
- Pipeline 1 – Modeling (e.g., step/frequency response modeling, parameter estimation, state-space modeling)
- Pipeline 2 – Analysis (e.g., stability and response analysis)
- Pipeline 3 – Fundamental Control (e.g., proportional/PD control, steady-state error, robustness concepts)
- Pipeline 5 – Pendulum Modeling (attachment pathway, as applicable)
- Pipeline 6 – Pendulum Control (optional extension, as applicable)
- Supplementary material (reference and extensions)
Experiment 2 – Attitude Control and Dynamics (Aero 2) – Group 2Rotational dynamics, parameter estimation, filtering, and control design delivered via a simulation-to-hardware workflow.
- The RAOP team selects a subset of Aero 2 modules to match the cohort pacing and deliverables.
- Participants use starter MATLAB/Simulink models to run simulations, interpret results, and tune controllers.
- Activities are scaffolded for educators who are new to control systems and simulation tooling.
- I0 – Hardware interfacing
- I1 – Block diagram modeling
- I2 – Rotor step response modeling
- I3 – Pitch parameter estimation
- I4 – System block diagram modeling
- I5 – Measuring and filtering
- I6 – Rotor speed control
- I7 – PID control design
- I8 – Qualitative PID tuning
- I9 – Gain scheduling
Experiment 3 – Manipulation and Sensing (QArm) – Group 3Manipulation fundamentals, sensing concepts, and pick-and-place workflows—first in virtual labs (digital twin), then reinforced through on-site hardware activities.
- The RAOP team selects a subset of modules to fit the cohort schedule and classroom translation goals.
- When available, selected activities align digital-twin practice with on-site hardware execution.
- Participants receive guided instruction; prior robotics programming experience is not required.
- Play (introductory activities)
- Task automation
- Surveying
- Pick and place
- Kinematic manipulation
- Velocity manipulation
- Visual manipulation
Experiment 4 – Ground Autonomy and Navigation (QBot Platform) – Group 4Mobile robotics foundations through a simulation-to-hardware workflow: teleoperation and sensing in virtual labs (digital twin), followed by structured on-site hardware activities.
- The RAOP team selects a subset of QBot activities aligned to cohort pacing and classroom feasibility.
- Selected activities include participant-facing materials (application guide, lab procedure, and assessment activity).
- Assessment prompts may include wheel-speed observations during maneuvers, camera feed comparisons, and depth camera vs LiDAR limitations.
- Activities are designed with classroom translation in mind (K–12 demonstrations and lesson integration).
- Play QBot (teleoperation and platform familiarization)
- Camera feeds and video observation (e.g., RGB vs downward-facing camera)
- Perception sensors overview (depth camera and LiDAR—capabilities and limitations)
- Digital twin (virtual) activities aligned to the on-site workflow
- Hardware activities (on-site) aligned to the virtual activities
- Application guide and step-by-step lab procedure materials
- Assessment activities aligned with the workflow (e.g., wheel-speed observations; sensor comparisons)
Follow RAOP
Updates, announcements, and participant highlights.
Official RAOP social channels. Additional platforms will be added as they launch.