Overview of all specs & issues

[kaskranenburgQ]

• 1. climate_spec

  • Purpose: Tests the effect of outdoor temperature changes on heating and cooling demands.
  • Test-load: 4 scenario's. based on the old nl 2050 scenario.
  • Run-time (local): 0:46
  • Category: Slidertest, 1 slider.
  • Effective: Small scope
  • Action: Review if this is still an aspect of the model we want to review.

• 2. biomass_spec

  • Purpose: Ensures balanced input/output flows for biomass.
    should this be added to that scenario? It's fine to still keep this test.
  • Scenario-load: 2 scenario runs. 1 based on the old nl 2050 scenario and 1 on an nvdt scenario.
  • Run-time (local): 4:18
  • Category: Balancing test.
  • Effective: Tests the entirety of the biomass sankey, but could be written more efficiently.

• Action: Review usage scenarios(the nvdt scenario could be changed In addition, we have added propane to the gasmix, this could also be implemented in the test). Finally, this could be set-up more efficient.

• 3. hybrid_heatpump_spec

  • Purpose: Tests various scenarios involving hybrid heat pumps.
  • Scenario's: 4 scenario runs, each based on the NL 2050 scenario.
  • Run-time (local): 0:25
  • Category: Slidertest
  • Effective: Small scope
  • Action: Review usage scenarios; heavily based on old scenario settings. Hybrid heat pumps do have some issues, so the test should be updated.

• 4. hydrogen_spec

  • Purpose: Checks supply/demand balance for hydrogen.
  • Scenario's : 14 scenarios in the preset collection.
  • Run-time (local): 2:05
  • Category: Balancing-test
  • Effective: Yes, but requires careful consideration of used scenario's.
  • Action: review scenario usage and check wether the commented tests can be used again.

• 5. lng_spec

  • Purpose: Focuses on LNG scenarios and infrastructure.
  • Scenario's: 2 scenarios, of which one is not used.
  • Run-time (local): 0:03
  • Category: Slidertest
  • Effective: Small scope
  • Action: Review relevance, and review the scenario that is used.

• 6. number_of_residences_spec

  • Purpose: Tests housing-related scenarios.
  • Scenario's: 5 scenarios
  • Run-time (local): 0:37
  • Category: Slidertest
  • Effective: Yes
  • Action: Review relevance, and review used scenario.

• 7. population_spec

  • Purpose: Checks working of population slider.
  • Scenario's: 1 scenario
  • Run-time (local): 0:23
  • Category: Slidertest
  • Effective: Yes
  • Action: Review relevance, and review used scenario.

• 8. primary_demand_spec

  • Purpose: Validates primary demand data.
  • Scenario's:: 14 scenarios in the preset collection.
  • Run-time (local): 2:26
  • Category: Balancing test
  • Effective: Yes, but requires careful consideration of scenarios used.
  • Action: Resolve issues with skipped tests, check wether these are resolved. Check relevance & used scenarios.

• 9. transport_spec

  • Purpose: Checks working of population slider.
  • Scenario's:: 1 basic nl to 2050 scenario.
  • Run-time (local): 0:06
  • Category: Slidertest
  • Effective: Small scope
  • Action: Review the used scenario. Review the skipped tests. Review tests, seem quite random.

• 10. washing_on_low_temperature_spec

  • Purpose: Analyzes the working of the 'washing on low temperatures' slider
  • Scenario's: 1 basic NL to 2050 scenario.
  • Run-time (local): 0:11
  • Category: Slidertest
  • Effective: Small scope, not really effective
  • Action: Replace with updated test.

• 11. emissions_electricity_spec

  • Purpose: Ensures consistency in emissions calculations.
  • Scenario's: 2 scenario's (ii3050, nvdt)
  • Run-time (local): 1:42
  • Category: Balanstest
  • Effective: Not sure yet. Needs more
  • Action: Keep. Review used scenario's.

• 12. flexibility_spec

  • Purpose: Tests flexibility options.
  • Scenario's: 7 scens are created. 1 is not used?
  • Run-time (local): 2:02
  • Category: Slidertest
  • Effective: Ineffective
  • Action: Activate Work In Progress section if needed. Check why tests are skipped. Why is one scenario created in the start of the script?

• 13. power_to_gas_spec

  • Purpose: Validates electricity mix for Power-to-Gas.
  • Scenario's: 14 scenarios in the preset collection.
  • Run-time (local): 1:51
  • Category: Balance test
  • Effective: Yes, but requires careful consideration of scenarios used.
  • Action: Check the tested scenario's.

• 14. chemical_industry_spec

  • Purpose: Analyzes scenarios related to the chemical industry.
  • Scenario's: 1 scenario is used, NL to 2050.
  • Run-time (local): 1:09
  • Category: Slidertest
  • Effective: Average
  • Action: Check issue concering test.

• 15. metal_spec

  • Purpose: Tests various scenarios for metal production.
  • Scenario's: 1 scenario is used, NL to 2050.
  • Run-time (local): 2:25
  • Category: Slidertests
  • Effective: Not entirely effectively written, but interesting.
  • Action: Check whether it still makes sense. It is a big test. Mathis might know more?

• 16. lole_spec

  • Purpose: Analyzes LOLE under different settings.
  • Scenario's: 1 scenario, nl to 2050.
  • Category: Dashboard item based on slidertests.
  • Effective: Not really, decreasing population does not necessarily lead to less LOLE.
  • Action: Check relevance.

• 17. merit_order_spec

  • Purpose: Tests the impact of merit order on electricity production.
  • Scenario's: 1 scenario, nl to 2050.
  • Run-time (local): 1:14
  • Category: Slidertest
  • Effective: Hard to say at first glance.
  • Action: Check relevance.

• 18. network_infrastructure_investments_spec

  • Purpose: Assesses network infrastructure investments.
  • Scenario's: 2 scenarios both nl to 2050.
  • Run-time (local): 0:52
  • Category: Slidertest
  • Effective: Hard to say
  • Action: Check relevance and update, seems outdated.

• 19. ** start_situation_spec**

  • Purpose: Assesses network infrastructure investments.
  • Action: Very old test, this does not test anything?
  • Test-load:1 scenario nl to 2040?

General remarks:

• Need to make a choice about which scenario's to use.
• Is 'nl' sufficient?
• Is the scenario creation we use efficient?
• How do we view the scenario's that are used in the testing?
• Some scenario's use a basis scenario in which the merit order is turned off, is this the same as the merit_order_off scenario?
• Check if an update in a test is seen as a new scenario, and how we can efficiently set up our test-suite.

Scenario_collection:

• II3050 V2
• IP
• DfE
• TYNDP
• Regional scenario's.

Open issues for tests:

• [Storage should get more specs] (Storage should get more specs #88)
  Necessity: Low
  Scenario's: If implemented, the whole scenario collection.
• [Create mechanical turk test for energy flow sankeys] (Create mechanical turk test for energy flow sankeys #122)
  Necessity: High, should be done for all of the supply and demand graphs.
  Scenario's: Whole scenario collection.
• [Run specs for random scenarios] (Run specs for random scenarios #145)
  Necessity: Low, I don't know if this is necessary. If we built a nice scenario collection, we don't have to make this I think.
• [Add spec to check whether all primary demand is accounted for] (Add spec to check whether all primary demand is accounted for #148)
  Necessity: High
  Scenario's: Whole scenario collection.
• [Add spec to test whether hourly loads and annual volmes add up] (Add spec to test whether hourly loads and annual volumes add up #149)
  Necessity: High
  Scenario's: Whole scenario collection.
• [Add spec to check whether application and final_demand groups return same CO2] (Add spec to check whether application and final_demand groups return same CO2 #150)
  Necessity: Not sure, might need coupling with molecule graph.
  Scenario's: Whole scenario collection.
• [Add spec to check whether primary demand per sector/carrier sums op to total primary demand] (Add spec to check whether primary demand per sector/carrier sums up to total primary demand #151)
  Necessity: High
  Scenario's: Whole scenario collection.
• [Add spec to test whether annual network gas demand equals supply] (Add spec to test whether annual network gas demand equals supply #154)
  Necessity: High
  Scenario's: Whole scenario collection.
• [Add spec to test whether annual steam hot water demand equals supply] (Add specs to test whether annual steam hot water demand equals supply #155)
  Necessity: High
  Scenario's: Whole scenario collection.
• Add spec checking dashboard values remain largely constant
  Necessity: High
  Scenario's: Whole scenario collection.
• Adding automated tests for new external coupling
  Necessity: Average
  Scenario's: Coupled scenario's within the scenario collection.
• Add spec to test whether hourly and yearly calculations add up
  Necessity: High
• Add spec to test whether graphs are in balance
  Necessity: High