-
Notifications
You must be signed in to change notification settings - Fork 10
Description
Describe the bug
A clear and concise description of what the bug is, including error messages.
Capacity is models of this type is often (but not always) defined in and energy unit per year, e.g. PJ/y. It indicates the amount of capacity that can deliver 1 PJ over an entire year. 1PJ is 277.78GWh. As there are 8760 hours in a year, this is equivalent to a capacity of 31.710MW. So when users enter e.g. a capital cost value for a technology, if they are using PJ/y, they should enter the cost of 31.710MW of output capacity.
This needs to be explained.
To Reproduce
Steps to reproduce the behavior. Attache any input file that might be required.
Expected behavior
A clear and concise description of what you expected to happen.
Users have reported this issue re documentation section "9.3.6. Existing Sectoral Capacity", but in reality it is an issue throughout the documentation. To address this, we need an additional sub-section in section 9 of the documentation that just deals with units in MUSE (i.e. explains that it's flexible and users can choose what they want, so long as they are consistent), along with a description of how to convert between various units to help people who are not from an energy background.
I see in FAQ there is already something like this, but it needs a separate section within the Inputs bit.
Screenshots
If applicable, add screenshots to help explain your problem.
Context
Please, complete the following to better understand the system you are using to run MUSE.
- Operative system (eg. Windows 10):
- MUSE version (eg. 1.0.1):
- Installation method (eg. pipx, pip, development mode):
- Python version (you can get this running
python --version):
Metadata
Metadata
Assignees
Labels
Type
Projects
Status