Ecalc 1379

[olelod]

Have you remembered and considered?

• I have remembered to update documentation
• I have remembered to update manual changelog (docs/docs/changelog/next.md)
• I have remembered to update migration guide (docs/docs/migration_guides/)
• I have committed with BREAKING: in footer or ! in header, if breaking
• I have added tests (if not, comment why)
• I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
• I have included the Jira issue ID somewhere in the commit body (ECALC-XXXX)

Why is this pull request needed?

This pull request is needed because of....

What does this pull request change?

Write summary of what this pull request changes if needed.

Issues related to this change:

[TeeeJay]

will this also apply to timesteps at the end of the global time vector, if e.g. the input file with regularity ends at 2024, but the global time vector goes to 2026? Often, it is (or was) set explicitly to 0 in the last timestep (for different type of data, regularity, produiction etc), as an explicit end to make sure that extrapolation worked for the few remainign timesteps at the end - and in that case regularity should be 0, and not 1...right?

[TeeeJay]

I guess this is correct for missign timesteps in the beginning and in the middle of the global time vector, but not at the end. or perhaps those in the middle should be interpolated (as you do I think?)