Hi Cuneyt, In this instance the noise parameter is just a straightforward addition of normally-distributed Gaussian noise of the specified amplitude to the initial condition. In fact, as far as I'm aware, the noise parameter has been superseded in deference to the awgn() function, which you can specify in the initial conditions through the expression evaluator, so this should be removed from the documentation. As our solver integrates the Navier-Stokes equations directly, there is no way to impose a turbulent inflow condition at present since we have no turbulence model. In fact prescribing these conditions is a relatively widespread problem for such solvers as far as I am aware. One of the alternatives may be to run a simulation of e.g. turbulent channel flow and use this time series as an inflow boundary condition. Don't know if anyone else on the mailing list might have a better suggestion. Cheers, Dave

On 12 Dec 2014, at 08:34, Cuneyt Sert <csert@metu.edu.tr> wrote:

Dear Nektar users,

Is the noise parameter used in Nektar the same as the classical turbulence intensity (http://www.cfd-online.com/Wiki/Turbulence_intensity)?

In Nektar's user guide it says that the noise parameter affects the velocity initial conditions. But we typically need to provide turbulence intensity at the inlets. Does this parameter remain effective at the inlets throughout an unsteady run?

Thanks in advance.

C. Sert

_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users

-- David Moxey (Research Associate) d.moxey@imperial.ac.uk | www.imperial.ac.uk/people/d.moxey Room 363, Department of Aeronautics, Imperial College London, London, SW7 2AZ, UK.