Set FLH of dedicated hydrogen offshore wind with 'regular' offshore wind input

[kndehaan]

Currently, we have two FLH sliders for offshore wind:

• flh_of_energy_power_wind_turbine_offshore sets the FLHs of 'regular' offshore wind and hybrid offshore wind
• flh_of_energy_hydrogen_wind_turbine_offshore sets the FLHs of offshore wind for dedicated hydrogen production.

It makes no sense that there's a separate slider for dedicated hydrogen production. Therefore, dedicated hydrogen production should be added to flh_of_energy_power_wind_turbine_offshore and flh_of_energy_hydrogen_wind_turbine_offshoreshould be removed.

This requires:

• Updating flh_of_energy_power_wind_turbine_offshore
• Updating flh_of_energy_power_wind_turbine_offshore_user_curve
• Removing flh_of_energy_hydrogen_wind_turbine_offshore

Note that as tackled in this PR, both the FLHs of energy_hydrogen_wind_turbine_offshore and energy_hydrogen_electrolysis_wind_electricity should be updated.

In addition, a migration should be written.

Tackles one of the steps mentioned in this issue quintel/etengine#1487 (comment)

[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.

[kndehaan]

Could be picked together with #3198

[kndehaan]

Discussion point: the start year value for FLH of offshore wind turbine for hydrogen production is dataset specific. For nl2023 for example, this is 4000 hours, which is different from the FLH of offshore wind which is 3397 hours.

Since we want the offshore wind FLH input to also set the FLHs of offshore wind with hydrogen, do we also want the FLHs in start year data to match? This would require changing the FLHs of energy_hydrogen_solar_pv_solar_radiation and energy_hydrogen_electrolysis_wind_electricity in the central_producers.csv for ETDataset datsets.

I think it would be neat to update the dataset values, but I don't feel it's required. @mabijkerk what do you think?

[mabijkerk]

I think it would be good to also update the FLHs in the datasets. I'm not a big fan of sliders that 'contain' multiple different start values, when they seem like a single start value to the users.

My main concern would be scenario migration. I don't see a very good way to write one for these changes, as making any changes to the offshore wind FLH would also affect the 'regular' offshore wind turbines. What do you think @kndehaan?

[kndehaan]

All right let's also do the dataset updates!

Regarding the migration, I think the reasoning is as follows:

If the regular offshore wind flh input has been set, as well as the flh input of offshore wind with electrolyser, then the regular flh input should be leading. This means that the flhs of offshore wind with electrolyser will be equal to the regular wind offshore. This doesn't require any action in the migration.

Optional: if regular offshore wind flh input has not been set, whereas flh input of offshore wind with electrolyser has been set, the regular flh input for wind offshore will be updated with the value of the flh input offshore wind with electrolyser.

I think I don't prefer the optional part, since I expect that more (unwanted?) scenario changes will occur as this will affect production of regular offshore wind. I expect there to be way more scenarios with installed capacity of regular offshore wind than offshore wind with electrolyser.

This would mean that the migration only has to remove the flh_of_energy_hydrogen_wind_turbine_offshore input.

@mabijkerk what do you think?

[mabijkerk]

I think I don't prefer the optional part, since I expect that more (unwanted?) scenario changes will occur as this will affect production of regular offshore wind. I expect there to be way more scenarios with installed capacity of regular offshore wind than offshore wind with electrolyser.

I also don't prefer the optional part. I think that we should indeed just remove the flh_of_energy_hydrogen_wind_turbine_offshore and then properly notify our users in the release notes.