kevmoor
commented
6 months ago Assembly
- need the placement of strut to blade and cable to blade and cable to strut, and strut/blade/cable to tower etc for each blade set. Ideal to have something arbitrary, like for regular HAWT just don't define anything, but for crossflow or bi-wing etc., then define the orientation and position of each component
- need the joint definition of each of those assembled components
- need to distinguish between rotating and non-rotating components especially what portions of the tower are rotating and if there are non-rotating guy wires.
Blade definition can be copied for struts and cables, I like that there is a 6x6 input option, which would work great for cables
May need custom input for control, think arcus where there was a control force on the center cables pulling the blades down like a bow. This is not mainstream for the current set of VAWTs and crossflow turbines though, so something to keep in mind, but probably don't need to implement now, maybe for very non-standard types of things, could just be put in the OWENS-specific yaml.
Then all of the OWENS specific - solver options, used discretization (as opposed to the defined discretization), are all defined there.
Use https://github.com/WISDEM/WEIS/blob/ct-opt/examples/17_MHK/RM1.yaml as a starting point.
https://windio.readthedocs.io/en/latest/
Look at existing, and identify where VAWT inputs are same and different. Implement Eventually bring in Pietro to review, and then bring to IEA folks.