Hi Chandra

yes standard functions like tanh(y),sin,cos  work with boundary conditions 
and with source terms, the random function doesn't work. So I would use a 
combination of the above standard functions to have an inlet bc or source 
terms that is space and time dependent.

Best
Giorgio

On Wednesday, August 26, 2020 at 8:47:53 AM UTC+2 Chandra Shekhar Pant 
wrote:

> Hello Giorgio,
>
> Thanks a lot Giorgio for your quick response and help. Really excited to 
> see this functionality in the PyFR.
> Is it possible to add something  like tanh(y) profile for the velocity at 
> the inlet and in addition to that would the random white noise like srand() 
> kind of function will work. Sorry for asking asking so many questions in a 
> single thread. 
>
> Sincerely, 
> Chandra Shekhar Pant
>
> On Tuesday, 25 August 2020 at 17:08:30 UTC+3 Giorgio Giangaspero wrote:
>
>> Hi Chandra,
>>
>> we will provide a patch relatively soon (say a month or two, I am doing 
>> the last test runs...) which will add synthetic turbulence generation 
>> capabilities to PyFR.
>>  In the meantime, if you are just interested in adding some fluctuations 
>> to the flow to trigger some instabilities, I would suggest using source 
>> terms, see [solver-source-terms] of the .ini file in the user guide*.*
>>
>> Best
>> Giorgio
>>
>> On Tuesday, August 25, 2020 at 9:16:06 AM UTC+2 Chandra Shekhar Pant 
>> wrote:
>>
>>> Hi all, 
>>>
>>> I am trying to simulate a jet using the PyFR. To trigger the 
>>> turbulence/instability I need to include the inlet/initial fluctuations in 
>>> the velocity field. Is this easily doable, how to do that? Any suggestion 
>>> and comment will help me a lot. Thanks in advance. 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "PyFR 
Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/pyfrmailinglist/2613a68e-8be2-41b4-9cc2-820abcccb111n%40googlegroups.com.

Reply via email to