gantech
commented
9 months ago Open gantech opened 9 months ago
gantech
commented
9 months ago gantech
commented
9 months ago Cases running with IEA 15MW power curve
JOBID PARTITION NAME ST TIME NODES REASON
13409608_10 standard iea15mw_fsi R 0:02 15 Prolog
13409608_11 standard iea15mw_fsi R 0:02 15 Prolog
13409608_12 standard iea15mw_fsi R 0:02 15 Prolog
13409608_13 standard iea15mw_fsi R 0:02 15 Prolog
13409608_1 weto iea15mw_fsi R 0:02 15 Prolog
13409608_2 weto iea15mw_fsi R 0:02 15 Prolog
13409608_3 weto iea15mw_fsi R 0:02 15 Prolog
13409608_4 weto iea15mw_fsi R 0:02 15 Prolog
13409608_5 weto iea15mw_fsi R 0:02 15 Prolog
13409608_6 weto iea15mw_fsi R 0:02 15 Prolog
13409608_7 weto iea15mw_fsi R 0:02 15 Prolog
13409608_8 weto iea15mw_fsi R 0:02 15 Prolog
13409608_9 weto iea15mw_fsi R 0:02 15 Prolog```
pscrozi
commented
9 months ago Simulations blowing up after 70-80 timesteps.
Rigid mode case has an issue.
pscrozi
commented
9 months ago Waiting on the rigid mode to work.
michaelasprague
commented
8 months ago Apparently IEA 15MW has only been run with elastodyn to date; Phil trying to get BeamDyn enabled.
pscrozi
commented
8 months ago Need to submit and let it run with FSI turned on. Nate should have an update tomorrow (10/16).
pscrozi
commented
8 months ago Nate ran rigid case out to a rotation or two. FSI case at 1 m/s and one at 12 m/s to be submitted. Neil got one started on Eagle this morning. Nate has one in the queue on Attaway and Skybridge.
Phil is working on a generalized build so that we can run on any Sandia HPCs. He is working out generalized submission so that we can submit that way and ask HPC team to manually elevate the priority.
Neil's case was breaking in OpenFast, but now working better once he changed the rotation rate. Parameters should be merged to the repo. Will chat about this on slack. Inconsistencies were fixed.
How many nodes should we be using for this case? 16 nodes for Nalu-Wind and 24 for AMR-Wind is what Nate is using on Attaway. 90 nodes total on Skybridge. Ideal would be 18 and 32.
Do we need all 13 points on the power curve? Ganesh says no, we can do with fewer.
pscrozi
commented
8 months ago Trying to automate OpenFast parameters. Run 6 different wind speeds, but none have run successfully so far. Dying on the Nalu-Wind side. Not stable in terms of displacements and RPM. Looking at turning tempo back on.
All files are on HFM repo. Please get eyes on this.
Negative volumes?
Had been doing 2 Picards, but need 4 Picards.
May need to run the OpenFast precursor for longer.
Try Elastodyn.
Where / how is it blowing up? What's the max velocity, max TKE? Displacement mapping ok or not? Need to viz it.
Reduce timesteps by 10x was required to get Beamdyn working and NM80. Currently using 5.5e-3 timestep in Nalu-Wind. Could try something even smaller.
Rigid case works. So mesh is ok and timestep is ok. Coupling to OpenFast may be to blame.
psakievich
commented
8 months ago Neil was able to get the case to run with elastodyn. Mike's suggestion of lowering the beam order made the beamdyn model run stably in openfast stand alone sims for over 70 seconds. Phil has kicked off fsi runs on chama using beam order 6 for wind speeds 5, 8, 10.59, and 14 m/s. Derek is working on porting beamdyn fixes to the fsi branch to see if that will help with higher order beam stability.
pscrozi
commented
8 months ago 8 m/s case is still running. We're at 2600 timesteps. All other wind speeds have failed. Nate and Neil found some inconsistencies in the input decks: hard codes values were missed. Updated and resubmitted. Beamdyn model is still behaving strangely: measured wind speed drops over time and goes to zero. Seems like a controller issue where the controller is oscillating so much that it turns off and the power drops to zero. We might need help from Derek and the OpenFAST team to help with this. We haven't heard anything back from Derek. We can submit the simulations and see if they can run, but seems like most of the issues are OpenFAST model issues.
psakievich
commented
8 months ago I resubmitted 5,8,10.59 and 14 m/s. I realized that the running 8 m/s case was using the mesh without pre-cone so I needed to start it over anyways.
pscrozi
commented
8 months ago They were running fine, but after 5500 timesteps (7 revolutions), they failed with negative volumes. Model continues to be somewhat touchy.
Still finding bugs in input files.
Nate: going through automation script and making sure everything is consistent for every wind speed. Lots of search and replace. Lining up timesteps and RPMs.
Derek said we were set up with OpenFAST model, but not even smaller timesteps. So we came up with a function of RPM for very small timesteps for BeamDyn, and backed out other parameters from there. There are little things we need to do before submitting the whole powercurve at once. Comes down to running with a smaller timestep, and lowering the beam order. Still working to make sure the parameters are all internally consistent.
Phil turned on the negative Jacobian check. Potential action item: when there's a negative volume, dump the files to see where the negative volumes are.
Neil has a couple of them running.