Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Warn about unrecognised columns in csv files

Open
#746 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
data-engineering

Research direction

Start by locating the CSV parsing and column-validation entry points, then inspect how recognized and optional columns are defined for inputs such as demand_slicing.csv. Done means extra or unrecognised columns produce a warning, including likely misspellings or unsupported fields, while valid files still load without crashing.

Written by the indexing model from the issue text.

Description

Currently, users can put extra columns in their csv files and MUSE will just ignore them. This is fine as there may be genuine use cases for adding extra columns so we wouldn't want it to crash.

However, I think we should at least consider raising a warning. Otherwise, it's quite possible that users could misspell an optional column (e.g. "startyear" instead of "start_year") and won't realise that the column isn't being read in.

Or they might put a "years" column in demand_slicing.csv thinking that demand slicing can vary by year (which it can't)

Dominant language
Rust
Stars
8
Forks
5
Avg merge
11h 31m
Merged PRs (30d)
33

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EnergySystemsModellingLab/MUSE2

All issues in EnergySystemsModellingLab/MUSE2

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.