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

Ability to run models for a subset of years

Open
#1,470 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
backend

Research direction

Start by tracing how milestone_years and inputs referring to milestone years are validated, then follow the model execution configuration. Done means users can select only the first n milestone years or use a reduced milestone-year granularity without invalid-input errors.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe

It's annoying that if a model is defined for a certain set of years, you HAVE to run the model for all those years (in most cases). If you tried removing years from milestone_years (say you only wanted to run the first year just for an initial test), it would complain about some of your inputs referring to milestone years that don't exist (e.g. an asset defined for 2040).

Describe the solution you'd like

I think we should allow:

  • running only the first n milestone years
  • running with reduced milestone year granularity (e.g. if the model is defined with a 1-year granularity, an ability to run it with 10-year granularity)

Some easy way for users to specify this

Describe alternatives you've considered

None

Additional context

Hopefully there wouldn't be any big implications that would make this difficult. Needs some thought though.

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.