You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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
amr.max_level
against tagging refinement levelssampling
,tagging
, andactuator
sections all have the correct inputs (no missing fields)For AcutatorFast runs:
Actuator.TurbineFastLine.density
matchesincflo.density
ICNS.source_terms
=ActuatorForcing
andincflo.physics
hasActuator
CompInflow=2
in fst fileWakeMod=0
in Aerodyn inputLet 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
Beta Was this translation helpful? Give feedback.
All reactions