Using energy units as metadata for default variables may limit applicability to non-energy sectors #511
FLomb
started this conversation in
Development
Replies: 2 comments
-
Possibilities for units from offline discussions:
This is very generic but tries to deal with the fact that each |
Beta Was this translation helpful? Give feedback.
0 replies
-
Moving out of beta and int oa discussion thread since it is not critical to anything in particular and could do with more dicussing with a wider audience. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem description
Model variables in the
math/base.yaml
file have been assignedunits
to populate the metadata. These units are currently energy specific, such as:energy
orpower
. Nonetheless, Calliope is generally applicable, and has been applied in the past, also to non-energy flows and amounts, for instance, CO2 or water flows and stored amounts. Energy-specific units would conflict with this liberty.One solution to have similar units but not energy specific might be to modify (i)
power
intorate
and (ii)energy
intoamount
, or something along these lines.Calliope version
0.6.11-dev
Beta Was this translation helpful? Give feedback.
All reactions