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

Include `regions` column for agent-related input files?

Open
  • Is something wrong?
#1,294 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
data

Research direction

Review how the commodity portions, search space, and objectives input files currently represent agent properties. Determine whether regional variation should be supported for all three categories, and identify the input validation and downstream modeling implications. Done means a decided scope and an agreed design for regional agent properties.

Written by the indexing model from the issue text.

Description

question

I'm wondering if we might want to allow users to have various properties of agents also vary by region, given that agents can operate in multiple regions.

We have separate input files for:

  • Commodity portions
  • Search space
  • Objectives

I think all of these could sensibly vary by region, too, though there's currently no way to express this. In particular, it strikes me as odd that agents have to be responsible for the same proportion of commodity demand for all regions in which they operate. Why, just because there's an agent that operates in, for example, different EU countries, would we assume it's responsible for the same proportions everywhere? Similarly, I can imagine a scenario where an agent can invest in coal power plants in one region, but not another, even though the power plant process type could operate in both (admittedly, this seems unlikely, but I don't think there's any reason we should prevent users from doing this). I have no idea whether it's sensible for agents to have different objectives in different regions, but, again, I don't see any good reason to prevent users from doing it.

I don't think this is esp high priority, but may be worth considering for future work.

Dominant language
Rust
Stars
8
Forks
5
Avg merge
17h 47m
Merged PRs (30d)
29

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.