External coupling inputs technical lifetime start and max value are incorrect for municipal and provincial datasets

[kndehaan]

Background
When trying to set external coupling inputs related to technical lifetime for a municipal or provincial region (via scenario-tools), it gives the following error (for example for external_coupling_industry_metal_aluminium_technical_lifetime):

Input external_coupling_industry_metal_aluminium_technical_lifetime cannot be greater than 2.041793032504091

This is a strangely low max value and seems incorrect, when looking at the input attributes of external_coupling_industry_metal_aluminium_technical_lifetime:

- query =
    UPDATE(
      V(industry_aluminium_external_coupling_node),
      technical_lifetime,
      USER_INPUT()
    )
- priority = 0
- max_value = 100.0
- min_value = 1.0
- start_value_gql = present:V(industry_aluminium_external_coupling_node, technical_lifetime)
- step_value = 1.0
- unit = year
- update_period = future
- coupling_groups = [external_model_industry, industry_metal_aluminium]

In this scenario for municipality Utrecht, I activated external coupling in the aluminium sector, but made no changes to the technical lifetime. It shows that the default value for technical lifetime is 2 years, where it should be 15 years:

These problems do not occur for a nl2019, no problems with setting the technical lifetime external coupling input and the default value is correct (15 years).

Problem
Something seems to go wrong with the technical lifetime external coupling inputs for municipal and provincial datasets, it seems that some scaling is happening of the start and max value. This problem occurs at least for:

• external_coupling_industry_metal_steel_technical_lifetime
• external_coupling_industry_metal_aluminium_technical_lifetime
• external_coupling_industry_metal_other_metals_technical_lifetime
• external_coupling_energy_heat_production_ht_residual_heat_technical_lifetime

To do:

• Find root cause of this bug
• Solve and check if inputs above behave properly
• Check if other external coupling inputs are also involved in this bug

[mabijkerk]

If I test it through the engine, everything seems to work. See SessionID 1310094 on production (#latest).

However, opening the scenario on etmodel, shows the screenshot below, see SavedScenarioID 19874. It's unclear to me where this max slider value of 0.20 comes from.

I think this is something for the developers to look into.

[noracato]

Could it be we have to add "years" to the unscalable units in etsource?

[github-actions]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[noracato]

I think a modeller should test if my unscalable unit solution is correct - so I'm adding it back to the modeller sprint

[kndehaan]

@noracato thanks for notifying, we'll address it in the Modeller sprint.