Don't force users to use turbine parameters coded in the library file
During optimization, users may wish to alter the turbine rating, hub height, or rotor diameter. The checks enforcing that such variables match what is in the turbine files make that difficult. I am on board with warnings perhaps, but I don't think a full turbine spec file should be required to slightly (or more than slightly) adjust hub height or turbine rating. We may need to consider how to handle this as Floris and pysam handle the inputs differently.
Proposed solution
Alternatives considered
Additional context