-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deficits show up in hourly calculations but not in yearly node #1389
Comments
Data-initialisation now shows 0 deficits in a blank scenario, nice work @noracato! I do still spot a minor issue however. Opening a blank scenario now produces -0 deficits: |
That is because the unit of the values is unknown, so the table does not (know how to) scale the values and keeps them as the are. |
How can the table know the unit of the values? Especially when there are two unit type values in the same table? |
Sorry, that was unclear of me. In the interface file, your table does not specify a unit, and therefore the table will not rescale values as it does not what the rules are for the conversion. Hence, giving the table cell a precision of 1 decimal will not do anything, as the table is not doing anything with the number. |
So is it possible to set a unit for part of the table? |
Not at the moment unfortunately |
Or we have to rebuild the table in a different way, like for example the plant profitability table |
Interesting! |
Background
When I open a blank
nl2019
scenario onmaster
, the deficits for households and buildings are 0.0 PJ. See thehouseholds_space_heater_deficit
:When I however open the deficits table, it shows that there are deficits for apartments between 2005 and present:
Issue
This means that the FEVER_DEMAND_CURVE and the FEVER_PRODUCTION_CURVE for
households_useful_demand_for_space_heating_apartments_2005_present
are not equal. These are subtracted from each other in the queryabsolute_deficit_useful_demand_for_space_heating_apartments_2005_present
.Solution
I am not sure how this should be solved. Some interesting points to note:
households_useful_demand_for_space_heating_apartments_2005_present
is the first of the existing households in thespace_heating_consumer_order
The text was updated successfully, but these errors were encountered: