You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often the unit for an energy price or cost has a magnitude format such as 'currency/kWh' or 'currency/kW' in the csvs. This works if we use kWh or kW correspondingly as units. But it is misleading in case we use, for example, kgH2 as unit. People might have a a tendency to pass those kgH2 to kWh as, for example, in the energy_price of EnergyProviders is indicated to input this value with a 'currency/kWh' format, but the optimizer is actually working with kgH2, if one has set it as unit. Therefore, the magnitude format for this energy_price (and other variables) should be 'currency/unit'.
The text was updated successfully, but these errors were encountered:
As far as I know, the unit in the csv file is up to the user to define, I should have time to test that soon as we need to make sure the use of unit is consistent for another project where we use MVS (This is essentially a GUI of MVS: https://github.com/open-plan-tool).
Often the unit for an energy price or cost has a magnitude format such as 'currency/kWh' or 'currency/kW' in the csvs. This works if we use kWh or kW correspondingly as units. But it is misleading in case we use, for example, kgH2 as unit. People might have a a tendency to pass those kgH2 to kWh as, for example, in the energy_price of EnergyProviders is indicated to input this value with a 'currency/kWh' format, but the optimizer is actually working with kgH2, if one has set it as unit. Therefore, the magnitude format for this energy_price (and other variables) should be 'currency/unit'.
The text was updated successfully, but these errors were encountered: