[albert.mink]

Hi, what about executing the program by

./venturi3d

[albert.mink]

Hi Klaus,

it sounds like you have compiled OpenLB wrong, because other programs are working fine with mpi.
Please ensure yourself that you clean the libraries (created some days before) by

make cleanbuild

Then check the Makefile.inc, see UserGuide http://optilb.com/openlb/wp-content/uploads/2016/03/olb_ug-1.0r0.pdf and compile the application again.

Regards,
Albert

[albert.mink]

Dear,

I am curious about your goal of including header of OpenLB. Do you want to use OpenLB Functions in your application or extend OpenLB by own code?

Regards,
Albert

[albert.mink]

Hi, please have a look to the user-guide. It is a manual for OpenLB:rnhttp://optilb.org/openlb/user-guidernrnStay tuned:rnIn march 2017 there will be a OpenLB spring school in Tunis.rnrnBye,rnAlbert

[albert.mink]

Hi Alejandro,rnrnwhenever you use a “”non standard”” descriptor, you better compile with the flagrnrnGENERIC (uncommend it on Makefile.inc)rnrnUsing PRECOMPILED, you can run D3Q19 and D2Q9 descriptors. Other causes compile errors.rnrnHope that your code runs now.rnrnAlbert

[albert.mink]

Hi Oli,rnrnare you really sure to have a DoVisualizationStuff() after EVERY collide and stream step? This is not recommended due to performance. Usually, computations and advanced post processing is strictly separated.rnKeep in mind, that LBM is formulated in meso scale and the raw data in OpenLB has to processed anyway, see prepareResults() in the given OpenLB examples. This ‘interal’ post processing is realized by the Functor concept.rnrnA quick and dirty work around would be, to write vtk data every time step and process is with a separate tool. As the output of OpenLB is VTK based, this provides a very general post processing for the user.rnrnBy the way, which data are you interested in? Macroscopic velocity, discrete particle distribution, …rnrnQ1: The examples of OpenLB call the function prepareResults(), where the internal post processing happens.rnQ2: Data hierarchy is from Cells to BlockLattice3D and SuperLattice3D. Where cells = raw data, the BlockLattice are a bunch of cells and SuperLattice is for Parallelisation.rnQ3: I am sure. Perhaps it need some adoption, but as it is open source this modifications are possible.rnrnLooking forward to your reply!rnAlbertrnrnHave a look to example aorta3d, there you will find fluxes!

[albert.mink]

Hi, did you manage to compile bste2d without any modification of the Makefile (openlb/examples/bstep2d/Makefile)?rnrnUnless you are using the original examples, you have not to change anything for the makefiles.

[albert.mink]

Hi Jose,rnrnin fact, I get the ‘debug’ message passou aqui from line ~74.rnThe program executes well up to line 220, with the output <starting simulation…>rnrnGuess the seg fault appears because of ill-posed dynamics or lattice coupling.rnrnAlbert

[albert.mink]

Hi Jose,rnrncollide operation is situated in src/dynamics/lbHelpers.h but also in the corresponding lbHelpers2D.h and lbHelpers3D.hrnStandard BGK-collision is called:rn bgkCollision()rnrnDid you already found the boundary conditions, like bounce back, in our code?rnrnAlbert

[albert.mink]

Hi Ivy,rnrnI think you are very close to the solution. If there are already .vti, .pvd files and you want to visualize them in paraview, then open the .pvd file with paraview.rnThe corresponding file is cylinder3d.pvd for this example.rnrn<FileNameGoesHere> is illustrated in the thermal3d example. It has two computation grids, which are written by two different vtkWriters. For the cylinder example you don’t really need more than one vtkWriter.rnrnAlbertrn

[Author]

Posts