Logging to CSV files in Raspberry Pi - Step-by-Step Execution

Concept Flow - Logging to CSV files

Start Program

↓

Open/Create CSV File

↓

Write Header if New File

↓

Collect Data

↓

Format Data as CSV Row

↓

Append Row to CSV File

↓

Repeat Data Collection

↓

Close File on Exit

This flow shows how a program opens or creates a CSV file, writes headers if needed, collects data, formats it as CSV rows, appends them, and repeats until the program ends.

Execution Sample

Raspberry Pi

import csv
with open('log.csv', 'a', newline='') as file:
  writer = csv.writer(file)
  writer.writerow(['Time', 'Temperature'])
  writer.writerow(['12:00', '22.5'])

This code opens a CSV file in append mode, writes a header row, then writes one data row with time and temperature.

Execution Table

Step	Action	File State	Data Written	Output
1	Open 'log.csv' in append mode	File opened (empty or existing)	None	Ready to write
2	Write header row ['Time', 'Temperature']	File open	Time,Temperature	Header added
3	Write data row ['12:00', '22.5']	File open	12:00,22.5	Data row added
4	Close file	File closed	All data saved	File closed properly

💡 File closed after writing header and one data row

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
file	None	Open file object	Open file object	Closed
writer	None	csv.writer object	csv.writer object	None
data_row	None	None	['12:00', '22.5']	None

Key Moments - 3 Insights

Why do we open the file in append mode ('a') instead of write mode ('w')?

Opening in append mode adds new data to the end without deleting existing logs, as shown in execution_table step 1 where the file is opened ready to add data.

Why do we write the header row every time the program runs?

If the file is new or empty, the header is needed for clarity. But if the file exists, writing the header again duplicates it. This is a common beginner mistake seen in step 2.

What does 'newline=""' do when opening the file?

It prevents extra blank lines in the CSV on some systems by controlling how line breaks are handled, ensuring clean rows as seen in the output column.

Visual Quiz - 3 Questions

Look at the execution table, what data is written to the file at step 3?

A Time,Temperature

B log.csv

C 12:00,22.5

D None

💡 Hint

Check the 'Data Written' column for step 3 in the execution_table

At which step is the file closed?

A Step 4

B Step 2

C Step 3

D Step 1

💡 Hint

Look at the 'Action' and 'File State' columns in the execution_table

If we open the file in write mode ('w') instead of append ('a'), what changes in the execution?

A File cannot be opened

B Existing data is erased before writing new rows

C Data is added to the end without erasing

D Header row is skipped

💡 Hint

Refer to key_moments about file modes and execution_table step 1

Concept Snapshot

Logging to CSV files:
- Open file with open('file.csv', 'a', newline='') to append
- Use csv.writer to write rows
- Write header once if file is new
- Append data rows as lists
- Close file to save changes

Full Transcript

This visual execution shows how a Raspberry Pi program logs data to a CSV file. It starts by opening or creating the file in append mode to keep old data. Then it writes a header row for column names if needed. Next, it collects data like time and temperature, formats it as a CSV row, and appends it to the file. Finally, it closes the file to save all changes. The execution table tracks each step, showing file state and data written. Variables like the file object and writer are tracked through the process. Key moments clarify why append mode is used, why headers might be duplicated, and the role of newline handling. The quiz tests understanding of data written, file closing, and file modes. This step-by-step trace helps beginners see exactly how logging to CSV works on a Raspberry Pi.