Computer Vision Course Syllabus
COMPUTER VISION: FROM OPENCV TO WORLD MODELS

Computer Vision: From OpenCV to
Vision-Language and World Models

Proposed Course Syllabus and Progressive Assignment Plan

1. Course Overview

This application-centered course develops computer vision systems from basic image operations to modern predictive visual intelligence. Students begin with image representation and OpenCV, then implement convolutional neural networks, train YOLO object detectors, apply ResNet transfer learning, fine-tune vision transformers, evaluate vision-language models, and construct a small predictive world-model pipeline. The course emphasizes data curation, reproducibility, robustness, model efficiency, ethical use, and the ability to explain what a system does, why its evaluation is valid, and where uncertainty remains.

Prerequisites. Python programming; basic linear algebra and probability; prior exposure to machine learning is helpful but not required. A short Python/PyTorch readiness module is provided during Week 1.

Instructional pattern. Each class follows a concept → guided demonstration → team laboratory activity → debrief/check → assignment sequence. Most class meetings prioritize implementation, analysis, and troubleshooting rather than extended lecture.

Computing environment. Python, Jupyter/Google Colab, OpenCV, PyTorch, torchvision, a YOLO implementation selected by the instructor, scikit-learn, matplotlib, Hugging Face tools, and Git/GitHub or an equivalent version-control platform. GPU access is recommended but not required for every assignment.

2. Course Learning Outcomes

By the end of the course, students will be able to:

Course learning outcomes, part one
OutcomeStudent CapabilityBloom's Level
CLO 1Explain digital image representation, color spaces, filtering, geometric transformation, features, and standard computer-vision evaluation measures.Understand / Analyze
CLO 2Implement reproducible image-processing and classical computer-vision pipelines with OpenCV.Apply / Create
Page 1
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
Course learning outcomes, continued
OutcomeStudent CapabilityBloom's Level
CLO 3Design, train, debug, and evaluate CNN, YOLO, ResNet, and vision-transformer models for classification and detection.Apply / Analyze
CLO 4Compare models using accuracy, class-level errors, robustness, latency, memory, and deployment constraints rather than relying on a single score.Analyze / Evaluate
CLO 5Use and evaluate vision-language models for zero-shot recognition, image-text retrieval, captioning, visual question answering, or grounded reasoning.Apply / Evaluate
CLO 6Implement a small temporal prediction or latent world-model experiment and explain how predictive representation learning differs from static recognition.Analyze / Create
CLO 7Curate and document datasets; identify bias, privacy, safety, licensing, and misuse concerns; and propose appropriate human-review controls.Evaluate / Create
CLO 8Communicate a complete computer-vision project through documented code, a technical report, quantitative evidence, a live demonstration, and an individual defense.Create

3. Learning Resources

No single textbook is required. Selected chapters, tutorials, documentation, and research papers will be posted in the LMS. Recommended references include:

  • Richard Szeliski, Computer Vision: Algorithms and Applications.
  • Official OpenCV and PyTorch documentation and instructor-provided notebooks.
  • Selected papers and technical readings on CNNs, YOLO, residual networks, vision transformers, vision-language models, JEPA-style learning, and world models.
  • Instructor-provided model cards, dataset cards, reproducibility checklists, and evaluation templates.

4. Assessment and Grading

Assessment and grading weights
Assessment ComponentWeight
Readiness quizzes and concept checks10%
GitHub-based programming assignments, laboratory reports, and demo videos45%
Midterm individual practical assessment10%
Final project: milestones, code, report, demonstration, and oral defense30%
Participation, peer review, and professional laboratory practice5%
Total100%
Page 2
COMPUTER VISION: FROM OPENCV TO WORLD MODELS

Every technical assignment is graded using a common evidence standard: functional correctness, experimental design, evaluation quality, reproducibility, interpretation of limitations, and responsible use of data and AI tools. A high accuracy value without a defensible evaluation will not receive full credit.

Letter grade scale
Letter GradePercentage
A90–100
B80–89
C70–79
D60–69
FBelow 60

5. Progressive Assignment List

The assignments move from controlled image operations to open-ended multimodal and predictive modeling. Every A0-A10 submission must be delivered as a standalone GitHub repository and an assignment-specific narrated demo video. The repository must contain executable code, environment information, quantitative results, representative visual outputs, a concise interpretation, an AI-use disclosure, and the exact video link.

Progressive assignments, A0 through A6
AssignmentTiming / WeightWhat Students BuildRequired Evidence
A0. Environment Setup and Image-as-Data DiagnosticWeek 1
3%
Load, inspect, visualize, and manipulate image tensors. Verify the Python, OpenCV, and PyTorch environment; explain image shape, channels, numeric range, and dtype.Standalone GitHub repository; narrated 3-4-minute demo video; notebook, setup report, five image operations, and a reproducibility check.
A1. OpenCV Image Processing LaboratoryWeeks 2–3
4%
Apply color conversion, resizing, cropping, filtering, thresholding, morphology, histograms, edge detection, and geometric transforms.Standalone GitHub repository; narrated 4-5-minute demo video; reusable OpenCV pipeline on a small image collection, with before/after evidence and parameter analysis.
A2. Classical Vision Mini-Application and Data AuditWeeks 3–4
4%
Build a contour-, feature-, or motion-based application. Examine annotation quality, imbalance, leakage, privacy, and licensing.Standalone GitHub repository; narrated 4-5-minute demo video; working application, dataset card, error cases, and a short ethics and reliability memo.
A3. CNN Image Classifier from ScratchWeeks 5–6
5%
Implement a CNN, construct valid training/validation/test splits, monitor learning, and diagnose underfitting or overfitting.Standalone GitHub repository; narrated 5-6-minute demo video; training code, learning curves, confusion matrix, class-level analysis, and final test results.
A4. CNN Robustness, Augmentation, and InterpretabilityWeek 6
4%
Compare augmentation strategies and test blur, noise, compression, occlusion, or domain shift. Inspect model attention using an approved method.Standalone GitHub repository; narrated 5-6-minute demo video; controlled comparison, robustness results, visual explanations, and a deployment recommendation.
A5. YOLO Custom Object DetectionWeeks 7–8
5%
Prepare bounding-box annotations, train or fine-tune a YOLO detector, and evaluate precision, recall, mAP, and failure modes.Standalone GitHub repository; narrated 6-7-minute demo video; custom detector, annotated examples, evaluation plots, error taxonomy, and an inference demo.
A6. ResNet Transfer Learning and Visual ExplanationWeek 9
4%
Fine-tune a residual network, compare frozen-feature and full fine-tuning strategies, and interpret predictions.Standalone GitHub repository; narrated 5-6-minute demo video; ResNet experiment, ablation comparison, class-level analysis, visual explanation, and model card.
Page 3
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
Progressive assignments, A7 through A10
AssignmentTiming / WeightWhat Students BuildRequired Evidence
A7. Vision Transformer Fine-Tuning and CNN ComparisonWeeks 10–11
5%
Fine-tune a vision transformer and compare it with a CNN or ResNet baseline using the same split and compute budget.Standalone GitHub repository; narrated 6-7-minute demo video; matched comparison of performance, data efficiency, latency, memory, robustness, and attention behavior.
A8. Vision-Language Zero-Shot Recognition and RetrievalWeek 12
4%
Use a CLIP-style or approved VLM for zero-shot classification and image-text retrieval; analyze prompt sensitivity.Standalone GitHub repository; narrated 5-6-minute demo video; prompt set, retrieval examples, quantitative results, subgroup errors, and prompt-design reflection.
A9. VLM Reasoning, Grounding, and Failure AuditWeek 13
4%
Evaluate an open VLM on captioning, VQA, or grounded reasoning. Identify hallucination, ambiguity, bias, and unsupported claims.Standalone GitHub repository; narrated 6-7-minute demo video; evaluation set, scoring protocol, failure taxonomy, grounding analysis, and a human-review policy.
A10. Predictive World-Model / JEPA-Style LaboratoryWeek 14
3%
Model temporal change in short image or video sequences through next-state prediction, latent prediction, or masked predictive learning.Standalone GitHub repository; narrated 6-8-minute demo video; predictive baseline, qualitative rollouts or latent analysis, error-over-horizon results, and comparison with static recognition.

Assignment Submission Standard

  • Each assignment must be submitted as a standalone GitHub repository with an accessible narrated demo video; the final project uses a separate repository and final video.
  • The repository must identify the exact release tag and commit hash being graded and must run from a clean environment using the submitted instructions.
  • The repository must include a README, environment or requirements file, source code, configurations, data documentation, results, a reproducibility check, an AI-use disclosure, and DEMO_VIDEO.md.
  • Training, validation, and test data must remain separated; any exception must be disclosed and justified.
  • Results must include class-level or case-level errors, at least one realistic failure condition, and a concise limitation analysis.
  • Images, datasets, code, pretrained weights, and external text must be credited according to their licenses and course rules; credentials, API keys, restricted data, and unauthorized large files may not be committed.
Page 4
COMPUTER VISION: FROM OPENCV TO WORLD MODELS

6. Assignment Workflow: GitHub Repository and Demo Video

Each assignment is managed as a small, reproducible software or research release. Students may accept a GitHub Classroom assignment or create a repository from the instructor template. The repository and video must represent the same tagged version. Work shown only in the video, but absent from the submitted repository, is not graded.

Common Development Workflow

Common development workflow
StageRequired ActionRepository Evidence
1. InitializeCreate or accept the assignment repository, clone it, review the specification, and confirm repository access.Initial commit; completed repository metadata; assignment issue or task list.
2. PlanDefine the task, dataset, success criteria, metrics, risks, and a realistic completion plan.README problem statement; data source; milestone checklist.
3. Establish baselineRun the starter pipeline or implement the simplest valid baseline before adding advanced components.Baseline configuration, output, metric, and dated commit.
4. ImplementDevelop modular code on a working branch and commit meaningful changes rather than one final code dump.Readable source files, configurations, commit history, and comments where needed.
5. Test and evaluateUse fixed splits, controlled comparisons, task-appropriate metrics, and representative success and failure cases.Test or validation script; saved metrics; plots; error examples; runtime or resource evidence.
6. DocumentExplain setup, data, commands, design choices, results, limitations, citations, and AI-assisted work.README; DATASET_CARD.md; MODEL_CARD.md when applicable; AI_USE.md.
7. ReleaseRun the repository from a clean environment, resolve broken paths, and tag the exact version for grading.Passing repository check; release tag such as v1.0; exact commit hash.
8. DemonstrateRecord a narrated screen demonstration of the tagged release, including a live run, results, and one failure case.DEMO_VIDEO.md with video URL, duration, recording date, release tag, and commit hash.
9. Submit and verifySubmit the repository URL, release tag, commit hash, and video URL through the LMS and complete any live verification.Accessible links before the deadline; instructor access; concise individual contribution statement.

Minimum GitHub Repository Standard

Each assignment must use a separate repository. A repository may be public or private according to instructor direction; private repositories must grant instructor access before the deadline. The minimum structure is:

  • README.md: problem, objectives, installation, data access, execution commands, results, failure analysis, limitations, and authorship.
  • requirements.txt or environment.yml, plus fixed random seeds and hardware or runtime information needed to reproduce results.
  • src/, notebooks/, configs/, tests/, data/README.md, results/, assets/, and docs/ organized so code, data instructions, and evidence are separated.
  • DATASET_CARD.md for every assignment using data; MODEL_CARD.md for A3-A10 and the final project.
  • AI_USE.md describing tools used, prompts or functions delegated, student verification, and any generated material retained in the submission.
  • DEMO_VIDEO.md containing the video URL, exact release tag, commit hash, duration, and a timestamped outline.
Page 5
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
  • .github/workflows/ with at least a lightweight structure, syntax, or reproducibility check. Large datasets and model weights should be linked or managed through approved storage rather than committed directly.

Demo Video Standard

  • Begin by showing the assignment title, student name, repository URL, release tag, and commit hash. The video must use the exact version submitted for grading.
  • Briefly state the problem, dataset, model or algorithm, and evaluation criteria; avoid spending most of the recording on slides.
  • Run the principal command or notebook section and demonstrate the system on at least one success case and one meaningful failure or limitation case.
  • Show quantitative results and explain what they mean. A metric screenshot without interpretation is insufficient.
  • Conclude with setup and reproduction instructions, known limitations, responsible-use concerns, and the student contribution when work is completed in a team.
  • Use readable screen resolution, clear narration, and captions. The video may be unlisted but must remain accessible through the end of the grading and appeal period.
  • Minor editing is allowed, but the recording may not conceal failed runs, substitute a different code version, or present another person's execution as the student's own.

Assignment-Specific Repository and Video Focus

Assignment-specific repository and video focus, A0 through A9
AssignmentGitHub Repository FocusDemo Video FocusLength
A0: Environment and image dataEnvironment check, image loading, tensor inspection, five basic operations, reproducibility log.Show installation check, image/tensor properties, operations, and one common setup error.3-4 min
A1: OpenCV processingReusable preprocessing pipeline with parameters, sample inputs, outputs, and comparison figures.Run the pipeline and explain how two parameter changes affect image quality or downstream behavior.4-5 min
A2: Classical vision applicationContour, feature, or motion application; dataset card; data-quality and ethics audit.Demonstrate success and failure examples, then explain one data or reliability concern.4-5 min
A3: CNN classifierTraining and inference scripts, split logic, curves, confusion matrix, checkpoints, and test results.Show training evidence, run inference, interpret class-level errors, and identify overfitting or underfitting.5-6 min
A4: CNN robustnessPerturbation and augmentation experiments, explanation maps, controlled comparison, and recommendation.Compare clean and corrupted inputs, show explanation maps, and discuss a deployment limitation.5-6 min
A5: YOLO detectorAnnotation instructions, training configuration, detector weights link, mAP results, inference script, and error taxonomy.Run detection on images or video, explain IoU or confidence behavior, and show missed and false detections.6-7 min
A6: ResNet transfer learningFrozen-feature and full fine-tuning experiments, ablation results, model card, and visual explanations.Compare the two strategies, run an example, and interpret a visual explanation and failure case.5-6 min
A7: Vision TransformerViT fine-tuning pipeline and a fair CNN comparison using matched data, metrics, and compute reporting.Demonstrate ViT inference and explain where ViT and CNN results differ under the same protocol.6-7 min
A8: VLM zero-shot and retrievalPrompt templates, embedding or retrieval pipeline, evaluation set, ranking metrics, and bias or sensitivity checks.Show zero-shot recognition or retrieval, compare prompt variants, and explain an incorrect result.5-6 min
A9: VLM reasoning and groundingEvaluation harness, prompt set, response logging, scoring rubric, grounding evidence, and failure taxonomy.Run representative questions, distinguish grounded from unsupported answers, and explain one hallucination.6-7 min
Page 6
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
Assignment-specific repository and video focus, A10 and final project
AssignmentGitHub Repository FocusDemo Video FocusLength
A10: Predictive world modelTemporal data pipeline, encoder and predictor configuration, latent or frame prediction evidence, and baseline comparison.Show a short rollout or latent prediction, compare with a baseline, and discuss uncertainty or compounding error.6-8 min
Final projectProduction-quality repository, tagged release, complete documentation, tests, baseline and advanced model, results, and team contributions.Present the integrated system, live execution, evaluation, failure analysis, reproducibility path, responsible-use limits, and individual contributions.8-10 min

Common Assignment Rubric

Common assignment rubric
CriterionWeight
Functional implementation and technical correctness30%
Experimental design, metrics, and failure analysis25%
GitHub organization, version control, reproducibility, and release quality20%
Demo video: clarity, live evidence, results, and limitation analysis15%
Documentation, citations, responsible use, and AI-use disclosure10%
Total100%

Submission gate. An inaccessible repository or video, missing instructor permission, missing release tag or commit hash, or a video that does not match the submitted code makes the submission incomplete until corrected. Any correction after the deadline is treated under the late-work policy.

7. Tentative 15-Week Schedule

Tentative schedule, weeks one through seven
WeekTopicsLaboratory FocusAssessment / Milestone
1Course orientation; image formation; pixels, tensors, channels, resolution; Python/OpenCV/PyTorch readinessGuided image-tensor laboratoryA0 assigned and completed
2OpenCV fundamentals: input/output, color spaces, transformations, filtering, thresholdingImage enhancement and preprocessing labA1 assigned
3Edges, contours, morphology, keypoints, matching, motion, and classical pipelinesClassical mini-application studioA1 due; A2 assigned
4Dataset curation, annotation, leakage, imbalance, augmentation, metrics, privacy, licensing, and biasDataset audit and evaluation labA2 due; project idea pitch
5CNN foundations: convolution, activation, pooling, receptive field, loss functions, backpropagationBuild a CNN from scratchA3 assigned; project proposal
6CNN training, regularization, augmentation, debugging, robustness, and interpretabilityRobustness and explanation labA3 due; A4 due; midterm practical
7Object detection fundamentals; bounding boxes; IoU; precision/recall; non-maximum suppression; YOLO architectureAnnotation and detector setup labA5 assigned
Page 7
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
Tentative schedule, weeks eight through fifteen
WeekTopicsLaboratory FocusAssessment / Milestone
8YOLO training, evaluation, error analysis, inference speed, tracking/deployment considerationsCustom detection challengeA5 due; project dataset/model card
9Residual learning, ResNet architectures, transfer learning, fine-tuning, and visual explanationResNet transfer-learning labA6 assigned and due; project baseline
10Vision transformer foundations: patches, embeddings, self-attention, positional informationViT fine-tuning labA7 assigned
11CNN–ViT comparison; data efficiency; robustness; compute; attention inspectionControlled comparative benchmarkA7 due; project progress review
12Vision-language models: contrastive learning, shared embedding spaces, zero-shot classification, retrievalVLM prompting and retrieval labA8 assigned and due
13VLM captioning, VQA, grounding, hallucination, bias, uncertainty, and evaluation designVLM failure-audit studioA9 assigned and due
14World models and predictive representation learning: temporal state, latent dynamics, masked prediction, planning conceptsWorld-model / JEPA-style predictive labA10 due; final project rehearsal
15System integration, deployment tradeoffs, project demonstrations, oral defenses, and course synthesisFinal showcase and individual defenseFinal project due

8. Final Project

Students complete an individual or small-team project that applies the full vision-system lifecycle: define a problem, curate data, establish a baseline, select an advanced model, evaluate the system, analyze failures, and communicate a defensible conclusion. Teams may contain two or three students, but every student completes an individual code walk-through and oral defense.

Required Technical Scope

  • A clearly stated problem, user need, and success criterion.
  • A documented dataset or data-collection process, including train/validation/test separation and a dataset card.
  • At least one baseline drawn from OpenCV, a small CNN, YOLO, or ResNet.
  • At least one advanced component drawn from vision transformers, VLMs, or predictive/world-model methods.
  • Evaluation using task-appropriate metrics plus robustness, efficiency, and qualitative failure analysis.
  • A discussion of bias, privacy, safety, misuse, licensing, uncertainty, and when human review is required.
  • A standalone GitHub repository with a tagged release, environment file, trained-model instructions, recorded demo video, and reproducible execution path.

Suggested Project Directions

  • Small-object detection in aerial, satellite, traffic, or campus imagery.
  • Visual inspection for manufacturing, infrastructure, or cyber-physical systems.
Page 8
COMPUTER VISION: FROM OPENCV TO WORLD MODELS
  • Medical, biological, environmental, or wearable-sensor image analysis using approved public data.
  • Multimodal image-text retrieval or domain-specific visual question answering.
  • Robustness and bias evaluation of a VLM on a carefully designed test collection.
  • Short-horizon prediction or latent state modeling for motion, navigation, robotics, or changing scenes.
Final project milestones
MilestoneDueEvidence
Problem and team registrationWeek 4One-paragraph idea, users, task, candidate data, anticipated risks.
ProposalWeek 5Two pages: motivation, related methods, data plan, baseline, advanced model, metrics, schedule.
Dataset and model cardWeek 8Data provenance, splits, annotation process, limitations, licensing, intended and excluded uses.
Baseline demonstrationWeek 9Runnable baseline with initial quantitative results and error examples.
Progress reviewWeek 11Advanced model status, ablation plan, unresolved technical risks, revised completion plan.
Rehearsal and peer reviewWeek 14Near-final demo, preliminary conclusions, peer feedback, revision checklist.
Final submissionWeek 15GitHub repository, tagged release, report, poster/slides, recorded demo video, live demonstration, and individual oral defense.

Final Project Rubric

Final project rubric
CriterionProject Weight
Problem definition and significance10%
Data quality, documentation, and responsible-use analysis15%
Technical implementation and correctness20%
Experimental design, baselines, and ablations15%
Evaluation, robustness, efficiency, and failure analysis20%
Reproducibility and code quality10%
Report, GitHub repository, recorded demonstration, presentation, and oral defense10%

9. Midterm Practical Assessment

The midterm is an individual, time-limited practical assessment covering image representation, OpenCV, data preparation, CNN concepts, code tracing, metric interpretation, and debugging. Students may be asked to modify a small pipeline, identify leakage or evaluation errors, interpret results, and explain their reasoning. Generative AI tools are not permitted during this assessment unless explicitly authorized.

10. Course Policies

AI-Assisted Work

Students may use generative AI and code-assistance tools for most learning activities and assignments, provided the use is disclosed and the student remains responsible for every submitted claim, line of code, result, and citation. Submitting unverified AI output, fabricated experiments, invented references, or code the student cannot explain is not acceptable.

Page 9
COMPUTER VISION: FROM OPENCV TO WORLD MODELS

Short oral checks, live code modifications, and individual assessments will be used to verify mastery. Restrictions for quizzes, the midterm, or other individual assessments will be stated in advance.

Academic Integrity and Reproducibility

Students may discuss concepts and debugging strategies, but submitted work must clearly identify individual and team contributions. Reused code, datasets, pretrained models, figures, and text must be credited. Results must be reproducible from the submitted materials. Fabricated data, altered logs, hidden test-set tuning, and unreported copying are violations of academic integrity.

Late Work

Assignments submitted within 24 hours after the deadline may receive up to a 10% deduction; work submitted between 24 and 72 hours late may receive up to a 25% deduction. Work more than 72 hours late may be accepted only when required for course continuity or supported by an approved accommodation or documented emergency. Project milestones should be submitted on time because they support feedback and team coordination.

Attendance and Laboratory Participation

Because the course is laboratory-centered, students are expected to attend synchronous sessions, participate in demonstrations and peer reviews, and maintain regular progress. Hybrid participation must follow the mode announced for that week. Missing a class does not remove responsibility for code, data, or milestone requirements posted in the LMS.

Data, Safety, and Responsible Use

Students must use datasets and systems consistent with university policy, applicable licenses, privacy requirements, and instructor approval. Projects involving identifiable people, sensitive records, surveillance, high-risk decision-making, or unsafe physical deployment require explicit approval and appropriate safeguards. Course work must not be used to make consequential decisions about real individuals.

Accessibility and Student Support

Students needing academic accommodations should use the university’s established process and communicate approved needs as early as possible. Course materials will be provided in accessible formats when feasible. Students experiencing technical, academic, or personal barriers should contact the instructor and relevant university support services promptly.