implement multi-farm support in pywake_api - #62
Conversation
|
Hi @kilojoules, I did a quick agent-based review. It found a few things. High
Medium
Low
|
|
is this only for pywake? can we setup a new example case, such that I can also adopt foxes to read multiple farms from windio? Thanks |
Address PR #62 review: - dedupe turbines across farms by full spec, not name; raise on same-name/different-spec conflicts - key hub_heights by global type index so specs with distinct hub heights no longer collide on per-farm "0" keys - take FUGA rotor diameter from merged specs instead of farms[0] - per-turbine AEP on same normalization basis as total, so per-farm AEP sums match the returned total - drop wall-clock assertion from multifarm test; assert outputs exist - fold duplicated create_turbines/_build_farm_turbine_list into create_turbine + _build_multifarm_turbines Add examples/cases/multiple_wind_farms from the IEA Wind 2200-22-MW Reference Offshore Wind Plant (Apache-2.0): three farms sharing one site and resource, for other tool APIs (foxes) to adopt. Multi-farm wind_farm arrays validate only against upstream IEAWindSystems/windIO schemas, so point the pin there; move AWAKEN cutin/cutout under performance to conform. Refs #61
|
Pushed 6ec490f addressing the review findings and adding the requested example case:
|
|
@bjarketol I think my coding agent adressed these things, detailed in the above message. Does this look OK to commit? |
|
@SchmJo I added a multi wind farm example |
|
@kilojoules Supported by foxes now. Added to foxes tests, and they are green. |
|
Second-round agent review (4 agents: fix verification, fresh bug hunt, data/schema/cross-tool, test adequacy), at 952e8cd. Round 1: all 8 findings verified fixed in 6ec490f — including numerically confirming per-farm AEPs sum to the total on both Weibull and time-series paths, and that New critical findings
Medium
Low
Verified goodType indexing matches Recommendation: hold merge until criticals 1–4 are addressed. Highest-value tests: multi-type single farm with 1-based keys, |
No description provided.