Jump to content

Course:FRE521D/Syllabus

From UBC Wiki
FRE 521D: Data Analytics in Climate, Food and Environment
FRE 521D
Section:
Instructor: Asif Ahmed Neloy
Email: asif.neloy@ubc.ca
Office: MCML 154
Office Hours: Mon/Wed 4:00 – 5:00 pm
In person, or by appointment
Class Schedule: Jan 6 – Feb 10, 2027
Mon/Wed 5:00 – 6:30 pm
Classroom: MCML 154
Important Course Pages
Syllabus
Lecture Notes
Assignments
Course Discussion


FRE 521D – Data Analytics in Climate, Food and Environment
2026/2027 – Term 2A (1.5 credits)

Land Acknowledgement

UBC's Point Grey Campus is located on the traditional, ancestral, and unceded territory of the xʷməθkʷəy̓əm (Musqueam) people. The land it is situated on has always been a place of learning for the Musqueam people, who for millennia have passed on their culture, history, and traditions from one generation to the next on this site.

Welcome to FRE 521D and Course Description

Welcome to FRE 521D, Data Analytics in Climate, Food and Environment. This applied course develops data analytics skills for economic, business, and sustainability decision making in the climate, food, and environment sectors. You will create reproducible data workflows using Python, SQL, APIs, and databases to acquire, manage, analyze, and visualize sector data, and explain the results to stakeholders. Applications include market forecasting, business performance, environmental risk, and sustainability measurement and reporting, with attention to data quality and uncertainty.

The course is organized by six sector topics: SQL and databases for climate and environmental decisions; APIs for climate, food, and economic data; automating food and environmental data pipelines; integrating climate and agricultural data for analysis; data quality and validation for sector analysis; and data visualization for climate, food, and environmental decisions. Each topic starts from a sector question and its data, and names the tools you use to answer it. Assignment 1 feeds Assignment 2, and both feed your final team project, so what you do in week 1 is still in use in week 6.

I work in applied machine learning, and I teach this course with one goal in mind: that you leave able to read, check, and explain every step of a data pipeline, whoever or whatever wrote it. That goal shapes the assessments below.

Prerequisites: none listed in the UBC Calendar. The course assumes the Python covered in the MFRE workshops and teaches SQL from the basics.

Course Details

Lectures Mondays and Wednesdays, 5:00 – 6:30 pm, MCML 154, in person. There are 11 sessions, from Wednesday, January 6 to Wednesday, February 10, 2027, for up to 3 contact hours per week.
Labs There is no separate lab section. Each lab is a notebook you complete outside class and submit on Canvas.

Lectures will be taught in person because it is the most effective way to engage with the topics that form a critical part of your learning. Lectures will not be recorded, because each session centres on live coding and discussion. If you have to miss a class, the lecture notebooks and supporting material will be available on Canvas, and you are welcome to clarify content during office hours.

What you will do: work through notebooks with me in class, try the practice exercises at the end of each notebook, complete five labs on your own, complete two assignments and a final project with your team, and write three quizzes and one short memo in class.

Instructor

Instructor Asif Ahmed Neloy, UBC Food and Resource Economics
Contact asif.neloy@ubc.ca or via Canvas. I typically respond to emails within 48 hours.
Office Hours Mondays and Wednesdays, 4:00 – 5:00 pm, MCML 154, in person, or by appointment

I invite you to attend office hours if you want to clarify course content, validate your understanding of the content, seek additional resources, or for any other purpose that can enhance your learning in this course.

Learning Outcomes

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

  • Identify when a climate, food, environmental, business forecasting, business-performance, or risk question calls for a data-driven approach, and select the SQL, ETL, or Python method best suited to answering it.
  • Apply SQL to build an analysis-ready data foundation for climate, food, environmental, and business analysis. Example: create an SQL access layer that integrates weather, crop production, and regional data for climate-agriculture analysis, tracking food and commodity prices, screening climate risk, and monitoring water- or air-quality thresholds.
  • Build an automated ETL data pipeline using Python to enrich climate-agriculture data with detailed weather data needed to analyze agricultural production, including extracting and transforming API data, integrating it into a relational database, validating data quality, and managing automated updates. Examples include combining weather and crop-production data, integrating market and commodity-price data, or preparing environmental monitoring data for analysis.
  • Use APIs to access and integrate current climate, market, food, and environmental data into analytical workflows. Examples include weather observations and forecasts, food-price indices, economic indicators, and environmental monitoring data.
  • Apply Python and SQL to analyze sector data and identify trends, seasonal patterns, regional differences, anomalies, and risks relevant to economic, business, sustainability, and environmental decisions.
  • Develop dashboards, visualizations, tables, and concise written briefs that translate climate, food, environmental, and business data into findings that support decision making.
  • Create reproducible and maintainable sector data workflows by documenting data sources, structures, transformations, quality checks, and processes so that the analysis can be reproduced, updated, or extended.
  • Read, trace, and explain SQL and Python code without assistance, and justify each data decision to a stakeholder.

Class Schedule

Week Topic Session focus, tools, and data Due or in class
Week 1
Wed Jan 6
(Lecture 1)
Topic 1: SQL and Databases for Climate and Environmental Decisions Course overview. Setup check for Python, Docker, MySQL, and Git. A climate station schema in a relational database: SQL and NoSQL, schemas, keys, data types, first queries. Tools: Docker, MySQL 8.0, SQL. Data: weather_stations and temperature_readings, two small sample tables entered by hand in class. Assignment 1 released. Teams due Sun Jan 10.
Week 2
Mon Jan 11
(Lecture 2)
Topic 1: SQL and Databases for Climate and Environmental Decisions A trustworthy SQL view for air-quality decisions: joins, CTEs, window functions, pivot and unpivot, and data contracts. Writing queries that flag readings above pollution thresholds and produce analysis-ready slices. Tools: MySQL 8.0, SQL, Python (pandas) for the CSV load. Data: Air Quality UCI. Final project released.
Week 2
Wed Jan 13
(Lecture 3)
Topic 2: APIs for Climate, Food, and Economic Data Extending a sector dataset from files with clear source provenance: structured ingest from CSV and JSON, encodings, raw and cleaned layers, lineage notes. Tools: Python, pandas, json. Data: crop_production_1990_2023 (FAO-style teaching file). Assignment 2 released. Lab 1 due Fri Jan 15.
Week 3
Mon Jan 18
(Lecture 4)
Topics 2 and 3: APIs for Climate, Food, and Economic Data; Automating Food and Environmental Data Pipelines Pulling economic data from public APIs: API requests, authentication, parameters, pagination, rate limits; then making the pull safe to rerun: retries, logging, safe reloads, and incremental pulls. Tools: Python requests, MySQL. Data: World Bank API, Frankfurter exchange-rate API (REST Countries described as a retired API); the Open-Meteo weather request for Assignment 2 is set up but not run in class. Assignment 1 due Sun Jan 17. Quiz 1 in class.
Week 3
Wed Jan 20
(Lecture 5)
Topic 3: Automating Food and Environmental Data Pipelines Is a food or environmental dataset fit to use? Column typing, reshaping, missing-data strategies (MCAR, MAR, MNAR), lightweight checks for ranges, keys, and nulls. Tools: pandas. Data: FAO Food Price Index cleaning exercise (practice table), simulated water-quality data. Lab 2 due.
Week 4
Mon Jan 25
(Lecture 6)
Topic 4: Integrating Climate and Agricultural Data for Analysis Combining climate and agricultural sources: multi-source joins with merge validation, pivot and unpivot patterns, preparing analysis-ready tables for downstream use. Tools: pandas. Data: crop production and climate tables (practice tables in class; Assignment 1 tables in Lab 3). Lab 3 due.
Week 4
Wed Jan 27
(Lecture 7)
Topic 4: Integrating Climate and Agricultural Data for Analysis From data to a decision: framing a decision question, choosing measures and groupings, descriptive summaries, simple trend checks. Tools: pandas, SQL. Data: FAO Food Price Index (monthly release of November 6, 2026). Quiz 2 in class. Lab 4 due Fri Jan 29.
Week 5
Mon Feb 1
(Lecture 8)
Topic 5: Data Quality and Validation for Sector Analysis Preparing sector data for analysis: European number formats and coded missing values, type coercion, dates and times, string normalization of category labels, hash and composite keys, de-duplication on a defined key, and a reusable cleaning pipeline. Tools: pandas. Data: Air Quality UCI, Global Weather Repository; FOOD-DATA-GROUP2 in the practice exercise. Assignment 2 due.
Week 5
Wed Feb 3
(Lecture 9)
Topic 5: Data Quality and Validation for Sector Analysis Validating sector data before it feeds a decision: profiling, missingness mechanisms (MCAR, MAR, MNAR) and handling strategies, outliers (IQR and z-score), value ranges and consistency rules, referential integrity checks, reproducible checks, and a quality score with a pass or blocked gate. Tools: pandas, NumPy. Data: Global Weather Repository; FOOD-DATA-GROUP1 in the practice exercise. Case study memo in class. Lab 5 due Fri Feb 5.
Week 6
Mon Feb 8
(Lecture 10)
Topic 6: Data Visualization for Climate, Food, and Environmental Decisions Communicating a climate or food finding to a decision-maker: storytelling figures from country-level temperature change and daily weather data, multi-panel figures, clear labels linked to the question, accessible colour. Tools: Matplotlib, Plotly. Data: FAOSTAT temperature change (climate_change_indicators), Global Weather Repository. Quiz 3 in class.
Week 6
Wed Feb 10
Topic 6: Data Visualization for Climate, Food, and Environmental Decisions (final team presentations) Team presentations of an end-to-end pipeline that answers a climate, food, or environment decision question. Code and slides due Tue Feb 9. Presentations in class. Report due Fri Feb 12. Quiz second sitting, if needed, Fri Feb 12.

All due dates are at 11:59 pm unless marked in class. The schedule may change. I will announce any change in class and on Canvas.

Learning Assessment

The learning assessment items below will keep us on track to meet the course learning goals.

Learning Assessment Activity Percentage Dates
Assignments (2), team 20% (10% each) Assignment 1: Sun Jan 17
Assignment 2: Mon Feb 1
Labs (5), individual 15% (3% each) Lab 1: Fri Jan 15
Lab 2: Wed Jan 20
Lab 3: Mon Jan 25
Lab 4: Fri Jan 29
Lab 5: Fri Feb 5
Group Project and Report, team 30% Code and slides: Tue Feb 9
Presentations: Wed Feb 10, in class
Report: Fri Feb 12
Quizzes (3), individual 30% (10% each) Quiz 1: Mon Jan 18, in class
Quiz 2: Wed Jan 27, in class
Quiz 3: Mon Feb 8, in class
Second sitting, if needed: Fri Feb 12, 5:00 pm
Case Study or Reading, individual 2% Wed Feb 3, in class
Participation 3% Throughout the course
Total 100%

Quiz minimum: to pass this course, you must also reach at least 50% on the quizzes, or on the second sitting described under Quizzes.

Assignments (20%, team)

The assignments are the two building blocks of your project. In Assignment 1, Building a Data Foundation for Climate-Agriculture Analysis, you use crop production and temperature anomaly data to design a relational schema, load and validate data, write queries with joins, CTEs, and window functions, and document table contracts and an analysis-ready view. In Assignment 2, Automating Climate Data Integration for Agricultural Analysis, you add daily historical weather from the Open-Meteo API to the Assignment 1 database: you extract data from a file source and a public API with rate limiting and retries, save raw and cleaned layers, validate and aggregate the results, and write run instructions.

You work with your project team of 3 to 4 students and make one submission per team on Canvas. Submit your team on Canvas by Sun Jan 10. If you do not have a team by then, I will assign you to one. Specifications and rubrics are on Canvas. Every team member is expected to understand all of the submitted work, because quiz questions draw on it.

Labs (15%, individual)

Five notebook labs, worth 3% each, give you hands-on practice with the methods from lecture. Each lab names the lecture it applies and is designed to finish in one sitting. Complete each lab yourself and submit it on Canvas. Labs are also your best preparation for the quizzes.

Group Project and Report (30%, team)

In the project, Climate Vulnerability Assessment for Global Agricultural Systems, your team integrates your work from both assignments into one pipeline and analysis that answers a client's decision question on food security and climate. The project grade is made up of a written report (50%), a presentation (30%), and a code repository (20%). The project brief and rubric are on Canvas.

The code and slides are due the day before presentations so that I can read your code before you present. The report is due after presentations, so you can use the Feb 8 visualization session and the questions you receive. Each team has 10 minutes to present, followed by 5 minutes of questions. Presentations fill the whole class, so I will stop each one at 10 minutes. Every member presents and answers at least one question. I choose who answers, and any member can be asked about any part of the code or analysis.

Quizzes (30%, individual)

The quizzes show what you can do by yourself, and they are how you and I find out whether the methods have stuck. Each quiz is worth 10%, runs for the first 25 minutes of class, and is written on paper. Quizzes are closed book, with no notes and no electronic devices.

Each quiz focuses on the topics below and can draw on earlier material. A quiz only tests what was taught in an earlier session.

  • Quiz 1, Mon Jan 18: Topic 1, SQL and databases for climate and environmental decisions.
  • Quiz 2, Wed Jan 27: Topic 2, APIs for climate, food, and economic data; Topic 3, pipelines that rerun safely and checks on whether a food or environmental dataset is fit to use; and the Jan 25 session on integrating climate and agricultural data.
  • Quiz 3, Mon Feb 8: the Jan 27 session on decision questions and trend checks, and Topic 5, data quality and validation for sector analysis.

Questions combine multiple choice, short written answers, reading and tracing code, and writing short SQL or Python by hand. Some questions use the code and data from your labs and assignments, for example by asking you to predict an output or change a step you have already completed. If you did that work yourself, these questions will feel familiar. Quiz questions draw only on labs and assignments due before that quiz.

Marks reward correct reasoning, not English fluency, in the quizzes, the memo, and the Delivery and Q&A mark. Small syntax slips in handwritten code do not lose marks when the logic is right. I will post sample questions on Canvas at least one week before Quiz 1. I will post each quiz's marks within 7 days, and Quiz 3 marks by Thu Feb 11.

Quiz minimum: to pass this course, you must reach at least 50% on the quizzes (15 of the 30 marks), or on the second sitting below. Take-home work cannot show on its own what you can do without help, so a passing grade needs evidence from both. If you reach neither, the highest course grade you can receive is 59%, which is a fail, because the minimum passing grade for master's courses at UBC is 60%. For example, a calculated grade of 72% with a quiz total of 45% becomes 59%. Your quiz total is not rounded for this check.

Second sitting: if your quiz total is below 50% after Quiz 3, you may write one 45-minute paper covering all three quiz topics on Fri Feb 12 at 5:00 pm. I will confirm the room on Canvas, and I will email you by Thu Feb 11 if this applies to you. Earning at least 50% meets the quiz minimum. It does not change your quiz marks, and it is not a make-up for a missed quiz or a supplemental exam. If you miss this sitting or earn less than 50%, the 59% limit stays.

Case Study or Reading (2%, individual)

In class on Wed Feb 3, you write a short memo by hand (20 minutes, no devices). I give you a printed description of a sector dataset. You link it to a decision question, state sources and assumptions, and propose a refresh cadence. This is the same framing your project report needs.

Participation (3%)

Participation rewards active engagement in class and in your team: attendance, discussion, peer feedback on pipelines, and timely progress check-ins. You can take part by speaking in class, posting on Canvas, or coming to office hours. I take attendance at each class, and team check-ins are short progress updates that I will announce in class. See the rubric under Course Policies.

Learning Materials

There is no required textbook and all required software is free, so the estimated cost of materials is $0. You need a laptop on which you can install software. Lecture notebooks, datasets, specifications, and the setup guide are on Canvas. The required readings below are articles and working papers available online or through UBC Library.

Required Readings

Applied research that shows how the tools in this course support sector decisions.

  • Adam, C., and P. K. Matta (2025). The Impact of Temperature and Rainfall Volatility on Food Prices: Evidence for Uganda. IMF Working Paper WP/25/244. Application: weather and food-price data integration, data preparation, seasonality, and anomalies (Topic 4).
  • Hsiao, A., J. Moscona, and K. A. Sastry (2026). Food Policy in a Warming World. Econometrica 94(2), pages 537 to 572. Application: a large, multi-source climate, crop, and policy dataset (Topic 4; introduction and data section).
  • Fanelli, R. M. (2026). Climatic and Socioeconomic Determinants of Consumer Food Price Index Dynamics: Empirical Evidence from 47 Advanced and Emerging Economies. Sustainability 18(16): 8455. Application: integrating climate, food-price, agricultural, and socioeconomic data across 47 economies (Topics 2 and 4).
  • Odion, D., et al. (2025). Towards Improving Farmers' Livelihood in Nigeria Using Food Price Forecasting. Journal of Agriculture and Food Research 24: 102365. Application: Python, ETL, APIs, and automated data pipelines behind a food-price forecasting system (Topics 2 and 3).
  • Gbadegesin, T., B. P. J. Andrée, and A. Braimoh (2024). Climate Shocks and Their Effects on Food Security, Prices, and Agricultural Wages in Afghanistan. World Bank Policy Research Working Paper 10999. Application: integrating climate, food-price, agricultural-wage, and exchange-rate data, with reproducible data and code (Topics 4 and 5).

Required Software

  • Anaconda (Python, Jupyter, pandas)
  • Visual Studio Code
  • Docker Desktop, running MySQL 8.0
  • Git

Recommended and Optional

  • Wes McKinney, Python for Data Analysis, 3rd edition.
  • Alan Beaulieu, Learning SQL, 3rd edition.
  • Claus O. Wilke, Fundamentals of Data Visualization, free online.
  • pandas User Guide: Python-based data manipulation and analysis.
  • MySQL 8.0 Reference Manual: relational database management and SQL.
  • DBeaver: database management and SQL interface.
  • Postman: API testing and exploration.

Datasets Used in Class, Labs, and Assignments

Dataset Used in Notes
MySQL weather_stations / temperature_readings Topic 1 (Jan 6) Five stations and 11 sample readings entered by hand in class; schema design, keys, data types, first queries
Air Quality UCI Topic 1 (Jan 11); Topic 5 (Feb 1) Hourly readings from one road-level monitor in an Italian city, March 2004 to April 2005; -200 codes a missing value
crop_production_1990_2023.csv Topic 2 (Jan 13); Assignment 1; Lab 3 Country, crop, and year production, area, yield, fertilizer use, and irrigation percentage; a modified FAO-style teaching file with planted quality issues
World Bank Indicators API Topics 2 and 3 (Jan 18) GDP per capita, population, and arable land; also the data for the retry, safe reload, and incremental pull examples; no key needed
Frankfurter exchange-rate API Topic 2 (Jan 18) European Central Bank reference rates; query parameters demo; no key needed
Open-Meteo API Topic 3 (Jan 18, setup only); Assignment 2 Daily historical weather; Lecture 4 sets up the request, and Assignment 2 adds the data to the Assignment 1 database; free for non-commercial use
REST Countries API Topic 2 (Jan 18) Retired version described in Lecture 4 as a warning example; v5 needs an API key
FAO Food Price Index Topic 3 (Jan 20); Topic 4 (Jan 27) Cleaning exercise on a practice table, then the real monthly FAO release of November 6, 2026 (2014 to 2016 = 100) for a decision question
Water-quality dataset (simulated) Topic 3 (Jan 20) MCAR, MAR, and MNAR missingness patterns
Global Weather Repository Topic 5 (Feb 1, Feb 3); Topic 6 (Feb 8); Labs 4 and 5 Daily weather for 210 countries, May to December 2024; string checks and composite keys (Feb 1); outliers, range rules, and quality scoring (Feb 3); figures (Feb 8)
FOOD-DATA-GROUP1 and GROUP2 Topic 5 (Feb 1 and Feb 3 practice exercises); Lab 1 Food nutrient values; practice exercises on cleaning (GROUP2) and outlier detection (GROUP1); Lab 1 loads GROUP2 into MySQL for SQL practice
FAOSTAT temperature change (climate_change_indicators.csv) Topic 6 (Feb 8); Lab 2 Country temperature change, 1961 to 2022, against a 1951 to 1980 baseline
Country temperature anomalies Assignment 1; Lab 3 Annual and monthly anomalies for 34 countries, 1990 to 2023

Strategies for Success

  • Finish the setup guide before our first class. If anything fails, bring it to office hours in week 1.
  • Come to every class and run the notebook with me. Reading finished code is not the same as writing it.
  • Attempt each lab on your own before you ask anyone or anything for help. The quizzes draw on the labs.
  • Do the practice exercises at the end of each notebook, then close the notebook and try one again from a blank cell.
  • Rotate tasks in your team so that every member writes, runs, and can explain part of each pipeline.
  • Practise by hand before each quiz: write a query on paper, and predict the output of a code block before you run it.
  • Ask early. Most problems in this course are quick to fix in week 2 and expensive in week 5.

Course Policies

MFRE program policies are presented in the MFRE Code of Conduct and on the Canvas course front page. The policies below are specific to this course.

Exam Policies

Quizzes, the second sitting, and the case study memo are written in person and follow the MFRE exam protocol. Calculators are not permitted. Before a sitting starts, switch off all electronic devices, including phones, smartwatches, earbuds, and smart glasses, and store them in your bag away from your desk. Having a device on you during a sitting breaks this rule. The only exception is assistive technology approved through the Centre for Accessibility. Papers are collected at the end of each sitting. Do not share any question with anyone until I confirm on Canvas that all sittings for that quiz are finished.

If you cannot write a quiz or the memo, contact me and Olivier Ntwali, MFRE Academic Program Coordinator, before it starts and provide documentation. If illness or an emergency stops you from contacting us first, contact us as soon as you can and I will consider an academic concession under UBC policy. If your absence from a quiz is approved, its weight is split equally across the quizzes you wrote, and the quiz minimum applies to those quizzes. If your absence from the memo is approved, its 2% is split equally across your quizzes. If approved absences mean you wrote fewer than two quizzes, we will arrange with you how the minimum applies. There are no make-up sittings for a missed quiz. A missed quiz or memo without an approved absence scores zero.

If you are registered with the Centre for Accessibility and eligible for exam accommodations, let me and the Program Coordinator know, and book each sitting through the Centre's exam reservation system at least 7 days in advance: Quiz 1 by Mon Jan 11, Quiz 2 by Wed Jan 20, the memo by Wed Jan 27, and Quiz 3 by Mon Feb 1. If you think you may need the second sitting, book it by Fri Feb 5. If you did not book and learn on Thu Feb 11 that you need it, tell me the same day and I will work with the Centre on your accommodation. If your sitting overlaps class, I will go through what you missed with you in office hours.

Assignments

Late work scores zero unless you arrange it with me by email before the deadline. This applies to labs, assignments, and the project. If illness or an emergency stops you from contacting me before a deadline, contact me as soon as you can and I will consider an academic concession under UBC policy. Please follow the file and naming instructions in each specification, and check that your ZIP opens before you submit it.

Regrading

If you think a mark is wrong, send me a written request within 7 days of the mark being posted, naming the item and your reason. I will re-mark the whole item, so the mark can go up or down.

Participation

Marks What it looks like
3 Attends at least 9 of the 11 sessions, contributes regularly in class, on Canvas, or in office hours, gives useful peer feedback, meets team check-ins, and receives a positive peer evaluation.
2 Attends at least 7 sessions, contributes at times, and meets most team check-ins.
1 Attends at least 5 sessions.
0 Attends fewer than 5 sessions.

Sessions missed with an approved absence count as attended in this table.

Group Presentations/Reports

The report, code, content, and slides receive one grade for the whole team. The Delivery and Q&A criterion (10 of the 100 project points, part of the presentation's 30) is marked individually. At the end of the project, each member completes a confidential peer evaluation, which informs Participation. If the peer evaluation and my own observations show that a member did not contribute, I may lower that member's project grade. The other members' marks do not go down because of it.

If your team has a contribution problem, please tell me early. If your team changes after Sun Jan 10, tell me right away and I will confirm in writing what the team still submits. If illness or an emergency stops you from presenting, contact me before class if you can. If your absence is approved, I will arrange another way for you to earn the Delivery and Q&A marks.

Plagiarism and Academic Integrity

Academic integrity means that the work you submit is honestly yours or your team's, and that you credit what came from elsewhere. It matters here because clients and policymakers act on an analyst's numbers without being able to check them.

In this course, cite your sources and any code you adapt. Labs, quizzes, and the memo are individual work, so do not share code or answers with anyone, including teammates. You may discuss ideas with other teams, but do not share code, API responses, or processed data with them. Examples of violations are copying a solution from a public repository or an earlier cohort, sharing quiz content, and using AI in a way the table below does not allow or without disclosing it. You are responsible for knowing these rules, so please ask me if you are unsure.

All suspected cases are escalated to the MFRE Academic Director and handled under MFRE and UBC procedures. Outcomes may include a reduced grade, a mark of zero on the work concerned, failing the course, or referral to the Dean's office or the President's Advisory Committee on Student Discipline. Read the Academic Calendar's statement on academic misconduct, and see Academic Integrity at UBC for guidance.

AI Use and Disclosure

Generative AI use is permitted on some, but not all, assessed work in this course. AI tools are part of professional practice, and you will likely use them in your career. You can only check their output if you can do the work yourself, so that ability is what this course assesses.

Assessment AI use What this means
Quizzes and second sitting Not allowed No tools of any kind.
Case study memo Not allowed Handwritten in class.
Presentation questions Not allowed Answers are live, with no devices and no outside help.
Labs Limited Attempt the lab yourself first. AI may explain an error message or a syntax rule in words. It may not produce code or answers that you copy into your lab.
Assignments 1 and 2 Not allowed No tools of any kind.
Project report, code, and slides Limited AI may help with debugging and with the grammar and clarity of text you have already drafted. It may not draft your report, slides, code, analysis, or conclusions.

Disclosure: end every lab, assignment, and project submission with an AI disclosure statement that names each tool, what you used it for, and which parts of the submission involved it. If you used none, write "No AI tools used." For team work, the statement covers every member's use, and every member is responsible for it. Disclosure does not make a use allowed that the table does not allow. Using AI where it is not allowed, or not disclosing it, may be treated as academic misconduct. Ordinary spell-check needs no disclosure, but tools that rewrite or suggest wording with generative AI do. If a use is not covered here, ask me before you submit.

Be ready to explain your work: you are accountable for everything you submit, whatever helped you produce it. I may ask any student to walk me through submitted work in a short meeting, for example when take-home and in-class work differ sharply. Being asked is not an accusation. Please attend within 5 working days of my request. If you do not attend, or cannot explain the work, I may refer the concern through the process above, where you can hear it and respond.

UBC Values, Policies, and Support

UBC provides resources to support your learning and well-being, and additional resources for times of crisis, including for survivors of sexual violence. UBC values respect for the person and ideas of all members of the academic community, and does not tolerate harassment, discrimination, or suppression of academic freedom. UBC provides appropriate accommodation for students with disabilities and for religious, spiritual, and cultural observances. UBC values academic honesty, and you are expected to acknowledge the ideas of others and uphold high academic standards. Details of the policies and how to access support are on the UBC Senate website.

For support in this course, use office hours and Canvas. For program matters, contact the MFRE Academic Program Coordinator, and see the MFRE Student Portal.

Syllabus version: November 18, 2026.