Cylinder3D Simulation gets aborted after changes in the dimensions.
- This topic has 13 replies, 3 voices, and was last updated 3 weeks, 4 days ago by .
-
Posts
-
Dear OpenLB team,
I made changes in the dimenssion of the stl file in which I made a new file where I extended the Y-axis upto 2000 mm using Solidworks and the others remain same. It gives out a message like this:[UnitConverter] ————————————————————-
[prepareGeometry] Prepare Geometry …
[SuperGeometry3D] cleaned 0 outer boundary voxel(s)
cylinder3d: ../../../src/functors/analytical/indicator/indicatorF3D.hh:643: olb::IndicatorCuboid3D<T>::IndicatorCuboid3D(olb::Vector<T, 3>, olb::Vector<T, 3>) [with S = float]: Assertion `_xLength>0 && _yLength>0 && _zLength>0′ failed.
AbortedI made changes in the code also where the make command doesnot show any error but still am getting the simulation aborted. The changes are given below:
// Instantiation of the STLreader class
// file name, voxel size in meter, stl unit in meter, outer voxel no., inner voxel no.
STLreader<T> stlReader( “cylinder3d.stl”, converter.getConversionFactorLength()/5, 0.001 );
IndicatorLayer3D<T> extendedDomain( stlReader, converter.getConversionFactorLength()/5 );// Instantiation of a cuboidGeometry with weights
#ifdef PARALLEL_MODE_MPI
const int noOfCuboids = singleton::mpi().getSize();
#else
const int noOfCuboids = 1;
#endif
CuboidGeometry3D<T> cuboidGeometry( extendedDomain, converter.getConversionFactorLength()/5, noOfCuboids );// Instantiation of a loadBalancer
HeuristicLoadBalancer<T> loadBalancer( cuboidGeometry );What is the issue? How to solve it? Please reply
As I said in the other thread where you posted the same question the likely issue is that your unit scaling is wrong. You can check this by e.g. opening both STLs in Paraview, the new one will likely be much smaller than the old one.
You can adjust the scaling in the STL reader arguments.
Obviously, once you have identified the differences between a working and a non working case this difference is a prime candidate for the problem.
You need to read and understand the cuboid geometry setup as well as the prepareGeometry function in order to identify what you need to adapt for your case.
I also, again, recommend a thorough read of the user guide lessons.
Dear atanuchaudhury,
thank you for posting. It is likely that you have to adapt your code to the new geometry loaded.
If this absolutely does not work, please consider using geometry primitives (indicator functors as in the 2D example) instead.However, we cannot offer full support on debugging your complete application.
You might want to consider taking part in our upcoming spring school for this.
More information is given here: https://www.openlb.net/spring-school-2025/BR
StephanThere is one thing you definitely should do: Read the user guide and do ateast a basic investigation of your problem yourself (e.g. read the code of the app, use a debugger, …)
Otherwise you won’t ever be able to do anything on your own using OpenLB.
- You must be logged in to reply to this topic.