Exawind / amr-wind

AMReX-based structured wind solver
https://exawind.github.io/amr-wind
Other
103 stars 78 forks source link

trouble in simulations results and some general queries #1103

Closed AsimUdel closed 1 day ago

AsimUdel commented 2 weeks ago

Hello All, I have run some simulations for my research (comprised of Spinup, followed by Precursor, and then Turbine). I have some questions and queries: 1) I plotted (wind speed and tke ), and TKE plots gave me some strange results. (Previously, also it seemed like the solution blew when I plotted wind speed with more than one turbines, some of Unstable case plots are Turbine_XZ_tke_plane_0)unstable e) Turbine_tke_xy_unstable input files are: Precursorunstable.txt Spinup_unstable.txt

2) Also, when I wanted to run “no turbine” simulations with the same times step as the turbine simulations, after (almost at 250s for Stable case, and 660s for Unstable, solutions blew up and stopped calculated variable i.e., velocity, tke, etc) Unstable_no_turbine Stable_no_turbine Input files are No_turbinestable.txt No_Turbineunstable.txt

3) A general question, when my simulations successfully completed, I got this message of " Unused ParmParse Variables", can someone explain what does that mean, are those variables unused in the simulations ? unused_parm_2 unused_parm_1

4) One of the experts from NREL suggested that when I am using OpenFAST with AMR-Wind, I should set “OpenMP flag to OFF” (https://forums.nrel.gov/t/tower-strike-with-latest-versions-of-openfast-and-iea-15mw/3024/84?u=raja.asim), my question is that should I set this flag to be Off for AMR-Wind too? (And can someone please comment on what will be the difference and implications, it will be helpful for new users like me, who have little knowledge about it) Thanks in advance.

marchdf commented 2 weeks ago

I can answer some of these easily. Others might want to way in for the other questions.

1-2. Looks like there are some CFL violations. I would turn down the time step. Or use a variable time step.

  1. "Unused ParmParse Variables": this has no impact on the simulation other than to tell the user that certain lines (inputs) in your input file were not used by the simulation. If you expected that, great, you can remove the lines from your input file and go on with things. Or just leave them in. If you didn't expect that, then you have an indication that you aren't doing what you thought you were doing ("huh that's weird I thought it would be using that input variable... I must have forgotten something else in the input file, maybe I forgot to turn on the physics I wanted")
  2. Yes openmp should be off for openfast (since many compilers complain about their usage of openmp). You probably want to set it to off in amr-wind as well though I don't think you have to. The question is: do you want to use openmp threading? This option might give a tiny boost on CPU (won't make a difference on GPU). But then you have an extra parameter to play with : threads/rank and how big of a thread block you want. All of which are performance tuning knobs that will be architecture dependent so you would have to discover those for your own architecture. Also (and this is work in progress) not all loops in amr-wind are threaded so you wont see much performance change there either. All in all, I wouldn't bother with openmp (and that will probably change in the future because these things always do).
AsimUdel commented 2 weeks ago

Hi @marchdf , Thank you so much for your answers. 1-2) I have re-run the simulations with the variable time step. 3) I wanted those variables in my simulations i.e., to have Stable atmospheric stability I gave certain value for "Abl.surface_temp_rate", which was not used. 4) Thank you, this is a bit technical, let me first see my architecture and then I can comment on this. I will leave this issue open for few days, maybe someone else might jump in, then I'll close it.

moprak-nrel commented 1 day ago

Hi @AsimUdel, closing this issue as it looks like your questions have been addressed. Feel free to reopen if there are any follow-ups.