Validating AMR-Wind inputs

[lawrenceccheung]

Hi everyone,

I'm working on some python code to make it easier for users to setup, visualize, and postprocess AMR-Wind cases (if you're interested, see https://github.com/lawrenceccheung/amrwind-frontend). One of the features @psakievich, @ndevelder, and I were thinking to include is a way to validate the input file before the case gets run -- basically check for silly mistakes or inconsistencies before precious queue time or CPU-hrs get wasted.

Here's an incomplete list of items I was thinking to check through the script

• Check sampling probe locations are actually inside domain
• Check amr.max_level against tagging refinement levels
• Check that sampling, tagging, and actuator sections all have the correct inputs (no missing fields)

For AcutatorFast runs:

• Check Actuator.TurbineFastLine.density matches incflo.density
• Check ICNS.source_terms = ActuatorForcing and incflo.physics has Actuator
• Check that all fst, aerodyn, servodyn, etc. input files exist
• Check OpenFAST timestep is multiple of AMR-Wind dt
• Check CompInflow=2 in fst file
• Check WakeMod=0 in Aerodyn input
• Check that turbine location is inside domain
• Check FAST output time with amr-wind restart time

Let me know if there's any others you can think of and would like to include. Some of these we can check in the code itself, at the pre-processing stage, or both.

Cheers,

Lawrence