[sagnikmazumdar]

Hi,

I wonder if there is a way to use profile data as inlet conditions in OpenFOAM. I mean I have a .dat file showing (x y z ux uy uz k epsilon) values at different points at the inlet which have come from very fine resolution measurements. I have attached an example velocity file as reference. I want to input this as boundary condition to a OpenFOAM simulation. I wonder how to do it. Would groovyBC work ?

Thanks for all the help.

Sagnik

[gschaider]

Originally Posted by sagnikmazumdar

I wonder if there is a way to use profile data as inlet conditions in OpenFOAM. I mean I have a .dat file showing (x y z ux uy uz k epsilon) values at different points at the inlet which have come from very fine resolution measurements. I have attached an example velocity file as reference. I want to input this as boundary condition to a OpenFOAM simulation. I wonder how to do it. Would groovyBC work ?

I'm afraid groovyBC won't work for you as it only supplies 1D-lookups (so something like "lookupRadial(r)*lookupTangential(alpha)" can work) but no general f(x,y,z) like you need it (it is not completely trivial to implement and I haven't needed it yet for a project. But of course: if someone wants to implement it ... I accept contributions)

But timeVaryingMapped might work for you (although you probably will have to reformat the data)

[sagnikmazumdar]

Thanks for the information. It seems for time varying condition we can only mention (time Ux Uy Uz) ! Is there a way to input location details as well like (time x y z Ux Uy Uz) ! Thanks again.

[gschaider]

Originally Posted by sagnikmazumdar

Thanks for the information. It seems for time varying condition we can only mention (time Ux Uy Uz) ! Is there a way to input location details as well like (time x y z Ux Uy Uz) ! Thanks again.

Please read carefully. I said timeVaryingMapped!!!

Quote from the comment in the source file

    Foam::timeVaryingMappedFixedValueFvPatchField

    Interpolates from a set of supplied points in space and time. Supplied
    data in constant/boundaryData/<patchname>:
        - points : pointField with locations
        - ddd    : supplied values at time ddd
    Points need to be more or less on a plane since get triangulated in 2D.