mathias
Forum Replies Created
-
Posts
-
Yes, that would be great. You could contribute an example yourself using https://gitlab.com/openlb/release.git olb-release or/and you join the OpenLB core devolper team..
You should check if your file is there similar to
// checks whether there is already data of the fluid from an earlier calculation
if ( !( superLattice.load( “fluidSolution_N”+std::to_string(N) ) ) ) {to avoid the segmentation faults since in your code it tries to read but without fall back. Have a look at the bifurkation example.
To compute the gradients, we need information of neighbour nodes and therefore we cannot overwrite the field we need to store once more the entire field!
THere is no pressure boundary condition for curved boundaries implemented!
According to https://www.openlb.net/forum/topic/material-assignment-indicator-is-changed-along-voxel-resolution/ I assume it is solve now — so it was not watertight!
Which code version, example and and code line are you exaclty talk about?
There are many ways to do that. One is to write a new post processor like the “ShanChen” ones..
This is a quite involving plan.. it goes beyond the scope of a forum. However, there are several ways to get support:
1/ Spring School
2/ Consortium/Support Licence
3/ Common Research ProjectYou can use as many stl files as you like for renaming the material numbers since the stl file is an Indicatr itself in OpenLB..
There are several ways to get detailed support:
1/ Spring School
2/ Consortium/Support Licence
3/ Common Research ProjectThere is a functor which directly computes the phys. pressure in si units for you, have a look at our many other examples in OpenLB. Further, it would be nice if you could share a video from you simulation with the community.. the pictues looking nice.
To get started the spring school is recommended, also for more involved consultuing, professional support can be requested, see https://www.openlb.net/consortium/ .
Might work with a combination of the defineRho (impose the rho distribution you want) method and the setPeriodicity
Currently, there is no code for spatial or Favre averaging in the released version. However, within the code of SuperLatticeTimeAveraged, it is possible to perform time-averaging for density, the physical quantity you want to observe, and the product of density and the physical quantity. This makes it feasible to calculate Favre averages.
For spatial averaging, since SuperLatticeTimeAveragedF3D inherits from SuperF3D, operator() is available. By inputting the coordinates of the physical quantity, it outputs the time-averaged data at that specific point. You can retrieve the time-averaged values at desired spatial locations and then spatially average the time-averaged values.
If you have a working version, please share with the community using the public OpenLB git!
You need to set both!