WISDEM
DFSM
Purpose
Adding in DFSM functionality into WEIS.
Type of change
What types of change is it? Select the appropriate type(s) that describe this PR
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (non-backwards-compatible fix or feature)
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no API changes)
- [ ] Documentation update
- [ ] Maintenance update
- [ ] Other (please describe)
Checklist
Put an x in the boxes that apply.
- [ ] I have run existing tests which pass locally with my changes
- [ ] I have added new tests or examples that prove my fix is effective or that my feature works
- [x] I have added necessary documentation
Hi Athul,
Thanks for adding this. It looks great so far. Do you need to merge in the latest ctopt? There seem to be a lot of extra changes besides the DFSM stuff. It's possible that the ctopt branch is also behind where you started this. We can discuss tomorrow.
818Nawaf is now blocked for the WISDEM organization. this account is likely a bot and had already been blocked for IEA Wind Task 37
Hi Athul,
Overall, this is looking great. I have it working locally with the latest ct-opt branch with some minor tweaks. It runs really fast as expected for a controller optimization.
I'm still missing how to make a DFSM model from a set of OpenFAST outputs. You don't need to post the whole set of outputs and test the routine just yet, but I'm not seeing from your documentation how to get started with that. It looks like something involving your Preprocessing notebook and the construct_LPV_matlab script. Can you write up the steps needed to generate a DFSM model from a set of OpenFAST runs?
Thanks for you contribution here. Looking forward to working with it.
Best, Dan
Let's continue the push on DFSM over here: https://github.com/NREL/WEIS-CTOpt/pull/2
Once that's in good shape, we can merge it back here for FOWTs.