[fk]

Dear Dylan,

maybe you need to first apply the “Resample To Image” filter. This can be found in Paraview under “Filters” then “Alphabetical”.

Best regards,
Fabian

[fk]

Dear Dylan,

the usage of the Gnuplot interface and its options can be found in the documentation. For example in the user guide, the developer guide, as well as in some examples, like laminar/cylinder2d.

Best regards,
Fabian

[fk]

Dear Junwei,

I am sorry for the late response, but the error was very tricky to find. Fortunately the bug is very easy to fix.

Please open the file “src/dynamics/guoZhaoDynamics.hh” and change in lines 67 and 116 from “this->_momenta.computeRhoU(cell, rho, u);” to “this->computeRhoU(cell, rho, u);“, i.e. remove “_momenta.”.

Best regards,
Fabian

[fk]

We’re working on it. If you find anything, it would be very helpful if you could post it here.

Thank you and best regards,
Fabian

[fk]

In release 1.3 the bug in GuoZhaoBGKdynamics has been fixed, therefore you can use either PorousBGKdynamics or GuoZhaoBGKdynamics.
See for example “olb-1.3r0/examples/porousMedia/porousPoiseuille3d”, where you can switch between both dynamics.

Best,
Fabian

[fk]

Dear Laurent,

could you please describe the error in more detail.
Which settings did you use, and does that change anything about the error?

Best,
Fabian

[fk]

Which Dynamics do you use? If you use the GuoZhaoDynamics, that could be the problem.
Or maybe your pin is too high, try something like 0.01.

[fk]

The code looks mostly fine, but try to smooth pin:

AnalyticalConst2D<T,T> rho(converter.getLatticeDensityFromPhysPressure(frac[0]*pin));

[fk]

Dear Ladasicr,

could you post the code of how you set the boundary conditions here? My guess is, that you do not have a smooth start up and this is why the simulation blows up.

Best,
Fabian

[fk]

Dear Ladasicr,

the problem may be due to bugs in the GuoZhaoBGKDynamics. These problems are now fixed and will be released soon. Until then you could try the PorousBGKDynamics based on the porous media model of Spaid and Phelan.

Best regards,
Fabian

[fk]

It is hard say without seeing the VTI file, but due to the DataArray name “AppendedData”, it looks like the format of the file is incompatible with the BlockVTIreader.

I would suggest to save your data in Ascii format, without compression. This can be done using ParaView using “Save Data” and then “Ascii” as “Data Format”.

[fk]

Hi,

lets assume you have following VTI file:

Quote:

dataFile.vti

Code:

<VTKFile byte_order=”LittleEndian” type=”ImageData” version=”0.1″>
<ImageData Origin=”-0.0014 0.01 0.0040″ Spacing=”0.00004 0.00004 1″ WholeExtent=”0 255 0 255 0 0″>
<Piece Extent=”0 255 0 255 0 0″>
<PointData>
<DataArray Name=”physVelocity” NumberOfComponents=”3″ format=”ascii” type=”Float32″>

You can then use the BlockVTIreader, and the BlockDataF3D, using the properties of the VTI file (filename “dataFile.vti” and DataArray name “physVelocity”):

Code:

BlockVTIreader3D<T,BaseType> readerData(“dataFile.vti”, “physVelocity”);
BlockDataF3D<T,BaseType> velocityF(readerData.getBlockData());

Then use the SpecialAnayticalF functor, for non-uniform grids, or the AnalyticalF functor to interpolate your data:

Code:

AnalyticalF3D<T,T>* solution;
solution = new SpecialAnalyticalFfromBlockF3D<T,BaseType>(velocityF, readerData.getCuboid(), spacing);

Where spacing is a Vector object, with the spacing information of the VTI file.

Code:

// Spacing=”0.00004 0.00004 1″
Vector<T,3> spacing(0.00004, 0.00004, 1);

Best,
Fabian

[Author]

Posts