Implement agent cost limits
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with agent_cost_limits.csv and trace where its capex_limit and annual_cost_limit fields enter the model, then inspect the appraisal optimisation and the flexible outputs discussion in issue #360. Before coding, resolve whether limits apply per commodity or across an agent and how milestone-year gaps and exhausted limits behave; done means agreed constraints are enforced, covered by tests, and the unused-input documentation or warning is addressed.
Written by the indexing model from the issue text.
Description
We have agent_cost_limits.csv with capex_limit and annual_cost_limit fields, but we don't use these anywhere in the model.
I have a vague idea of what these might entail:
capex_limit: total amount an agent can spend per milestone year (or per year, in the case where there's a gap between milestone years?) on capital costsannual_cost_limit: total amount an agent can spend per milestone year on operating costs
Some questions @ahawkes:
- presumably we implement these are constraints in the appraisal optimisation?
- what happens when these limits are reached? No more investment allowed for that agent? In which case, if there's still unserved demand for that agent then it will fail. Perhaps this makes more sense for "compete" commodities, where other agents would potentially be able to make up the rest of the demand
- are these limits for each commodity, or total across all commodities that the agent serves? If the latter, then the order we solve the commodities is important, as commodities solved first could potentially fill up the agent's quota. Perhaps we'd have to solve all the commodities that the agent serves simultaneously, similar to what I've proposed for flexible outputs (#360). That would require all the commodities that the agent serves to be the same rank in the commodities graph - could be a problem, although for most common scenarios I think it wouldn't be
In any case, until we implement this I suggest we temporarily turn off the input file, or at least add a warning to the documentation that this file isn't being used.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 5
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 33
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EnergySystemsModellingLab/MUSE2
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
EnergySystemsModellingLab/MUSE2#1367 · 1 comment ·
-
Remove the `ironing out iteration 0` prefix from debug files when the ironing out loop is turned off Openmuse xiii question
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
EnergySystemsModellingLab/MUSE2#1221 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
EnergySystemsModellingLab/MUSE2#1554 ·
-
bug
EnergySystemsModellingLab/MUSE2#1541 · 2 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
EnergySystemsModellingLab/MUSE2#1526 ·
All issues in EnergySystemsModellingLab/MUSE2
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#255 ·
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
raphamorim/rio#1956 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comment ·