Quantify wind speed shift

[samuelwnaylor]

In similar way that power curve, rpm and pitch shifts are already calculated, the change in this PR adds wind speed shift to the calculated ops curve shifts.

A refactor on the ops curve shift functionality was performed as part of this PR to improve readability and ease of adding further shift calculations if required in future.

[aclerc]

At a high level this looks very good. I like the new ops_curve_shift.py module and appreciate the thorough testing of it. Could you please re-run the smarteole notebook as part of this PR? This way the PR will include a real-world example of the new wind speed drift calculation for sanity checking.

[samuelwnaylor]

At a high level this looks very good. I like the new ops_curve_shift.py module and appreciate the thorough testing of it. Could you please re-run the smarteole notebook as part of this PR? This way the PR will include a real-world example of the new wind speed drift calculation for sanity checking.

Addressed in commit 6ff04f8

[samuelwnaylor]

I've added the running and maintenance of smarteole_example.ipynb to GitHub Actions so that it is no longer a requirement to re-run the notebook manually before PRs are approved and merging into the main branch. In summary the change implements:

• The .ipynb in the repo is stored without any cell execution or outputs (to ensure this is maintained in this state, the cell outputs are checked for emptiness as part of the CI, see the command poe smarteole-nb-clear-output --check)
• The GitHub Actions executes the notebook and stores as html as an artifact. This artifact is attached to the action run and may be downloaded for review.

[UPDATE] The Smarteole example notebook is executed in the smarteole_example.yaml workflow on merge to main. The workflow may be triggered manually (workflow_dispatch:), which could be used if the PR review would like to see the notebook output before merge to main.