lawrenceccheung

Should we wait until we have the equivalent examples in amr-wind, and then remove them here? Lawrence

Expanding on @psakievich's point a bit, maybe we can somehow link the example cases to the regression test, except increase the simulation time or add additional outputs (we can also...

Yeah, the example cases are a bit out of date. For the ABL case, I would start with https://github.com/Exawind/nalu-wind/blob/master/reg_tests/test_files/ablNeutralEdge/ablNeutralEdge.yaml or possibly this case https://github.com/Exawind/wind-energy/blob/master/Pedersen_N02/NaluWindRun02/nalu_neutral_v3.yaml, and for the actuator line turbine...

Hi @genevievestarke, @mbkuhn, It could be worth asking @ewquon, what you're asking for might be very closely related to the meso-microscale coupling. Beyond just specifying the MMC profiles, there is...

I agree with @psakievich, if we decide to deprecate all previous versions of OpenFAST, we'll need to very clear to the user base that this is happening, and that to...

Also tagging @ndevelder on this.

Not sure if this helps any, I compiled `RelWithDebInfo` and then ran it again. Here's the gdb core information: ``` #0 0x0000000000370621 in amr_wind::diagnostics::get_macvel_max(amrex::MultiFab const&, amrex::iMultiFab const&, int, double)::$_2::operator()(amrex::Box const&,...

It's not super-urgent, most projects that I'm aware of will be relying on older, established versions of OpenFAST to do their runs. But be aware that compiling with OpenFAST will...

On Frontier a specific version of OpenFAST needs to be used right now. AMR-Wind doesn't work with version v3.5.0, but also doesn't work with v3.4.1: ``` 5 -- Cray Programming...

@neilmatula and I are realizing that the `actuator_src_term[x,y]` output is dependent on mesh resolution, which makes it hard to compare against literature. So I added `f_theta` and `f_z` output to...