After PR #84 is merged, the user will be able to generate inflow velocity data outside of PVade and then feed that data in as inflow boundary conditions. I currently use pyconturb to generate this inflow turbulent data. If that ends up being the best tool, it would be great to integrate pyconturb directly into pvade so that the user can just select "turbulent_inflow" in the input .yaml file and pvade would then call pyconturb to generate the inflow data internally.
After PR #84 is merged, the user will be able to generate inflow velocity data outside of PVade and then feed that data in as inflow boundary conditions. I currently use
pyconturbto generate this inflow turbulent data. If that ends up being the best tool, it would be great to integratepyconturbdirectly intopvadeso that the user can just select "turbulent_inflow" in the input .yaml file andpvadewould then callpyconturbto generate the inflow data internally.