Missing top level config values
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 55
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Version Checks (indicate both or one)
-
This bug exists on the master branch of PyPSA-USA.
-
This bug exists on the develop branch of PyPSA-USA.
The Issue
The develop branch seems to be missing key config values in the tracked default config.yaml. Notably I have run into errors due to missing values for
renewable_land_access: reference
unsure why as the values should be inherited from the config.common.yaml
Steps To Reproduce
No response
Error Message
Anything else?
No response
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Compare the tracked default config.yaml with config.common.yaml, focusing first on renewable_land_access and how shared values are expected to be inherited. Trace the configuration-loading entry point to determine whether the value is omitted from the tracked file or inheritance is failing. Done means the develop branch loads the expected top-level value without the reported missing-config error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100