FBukreev
Forum Replies Created
-
AuthorPosts
-
FBukreevKeymaster
Hi, you can try to apply the wall model to aorta and it will calculate y distance and u_tau. Then in Paraview you can visualize both fields and calculate y+ from them, or create a new lattice functor which takes these values from external fields and calculates y+.
FBukreevKeymasterHi, you can try to apply the wall model to aorta and it will calculate y distance and u_tau. Then in Paraview you can visualize both fields and calculate y+ from them, or create a new lattice functor which takes these values from external fields and calculates y+.
FBukreevKeymasterYou can try to do DNS with ThirdOrderRLBdynamics and D3Q19. That should give correct mass.
Actually, BGK with D3Q27 should also work, I dont see any reasons why it can loose mass.
FBukreevKeymasterDear Nipin,
please take for DSN the ThirdOrderRLBdynamics, the standard RLB dynamics doesnt work well.
And for the vortex method, please use it always inside one cuboid, because it is not parallelized. You can make inlet inside of one cuboid and the rest can be separated as you wish.
Best,
FedorOctober 27, 2025 at 1:35 pm in reply to: Turbulent channel flow: DNS relaminarizes and LES shows wavy flow at finer grid #10896FBukreevKeymasterHi,
BGK at higher resolution should give the turbulent result, because BGK has very low numerical diffusion itself.October 20, 2025 at 9:53 am in reply to: Turbulent channel flow: DNS relaminarizes and LES shows wavy flow at finer grid #10826FBukreevKeymasterHello,
if you want to make DNS, then BGK and bounce back should be enough. Sometimes by too small time steps the flow becomes strange. You can try to take higher lattice Velocity in the converter if your maximal CFL number during actual simulation is too low.
September 24, 2025 at 10:10 am in reply to: Computing Pressure Statistics with PostProcessors #10753FBukreevKeymasterHello,
to obtain pressure you need to compute denisty with computeRho() and then make (density – 1)/descriptors::invCs2
(). That will give you pressure in lattice units. FBukreevKeymasteryes, you understand correctly. LATTICE_TIME is already existing, you can define RMS_VELOCITY in the descriptors/fields.h
FBukreevKeymasterok, for that we have not implemented a gpu-capable postprocessor. You can how the averaging is performed now and try to extend it with the required statistics evaluation.
FBukreevKeymasterIn the last release these functors are not used in general, check the actual release.
FBukreevKeymasterIn the actual realease of openLB the averaging happens already on GPU and you dont need any separate functor.
FBukreevKeymasterHello,
the cumulant dynamics was only a prototype, which was tested only by taylor green vortex example. If you want to simulate the channel case it is better to use the standard HRR collision with wall model.
FBukreevKeymastersorry I cannot understand the reason for the problem on that way. It could be also numerical paameters that you use. The divergence time step should be also investigated carefully.
FBukreevKeymasterHi,
I would add zeroGradient boundary conditions for ADE lattice to the inlet and outlet of the channel and in the coupler you can comment out the Boussinesq force if you dont consider it.
FBukreevKeymasterHello,
We have not added the fringe zone at the outlet. This is only an example of turbulent flow with an airfoil indicator and wall model. More advanced setups will be introduced in the next release.
-
AuthorPosts
