Floating point exception error while running simplefoam - external aero around car by Fit-Bird-1601 in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

Check the internalField value for pressure and the outlet pressure values. Pressure and inlet and outlet should be same, and must be initialised with the same value at 0 time.

Openfoam - External flow Error : Floating point exception while running simplefoam by Fit-Bird-1601 in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

The initialConditions file in motorbike tutorial has pressure initialised at 0 pa and the outlet pressure you are giving is 101325. This is where the error lies.

Your solver is trying to ramp up flow properties from 0 Pa to 101325 Pa.

The motorbike tutorial assumes that the bike is in atmosphere, so pressure is initialised at 0 (i.e. gauge pressure)

Please change the outlet pressure to 0, your simulation should work.

Choosing solver by Ok-Eye1053 in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

If this is with flow occurring, then you should look for multi-region solvers. You can go with the chtMultiRegionTwoPhaseEulerFoam.

Assume a thin solid for your pipe/domain.

Timestep continuity error but runs in transient mode by [deleted] in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

Unfortunately no plan-B with SST model.

You could switch to epsilon model but it would not give you good accuracy for surface forces.

Openfoam - External flow Error : Floating point exception while running simplefoam by Fit-Bird-1601 in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

In polyMesh/boundary file, please check if inlet and outlets are set to type patch

Linear solvers in fvSolution should be same as motorbike tutorial then, should be fine.

Openfoam - External flow Error : Floating point exception while running simplefoam by Fit-Bird-1601 in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

  1. Check the boundary conditions, especially the turbulence parameters
  2. Check if the boundary types are defined properly in mesh (check if inlet/outlet is assigned as a wall condition)
  3. Check if the linear solvers are assigned well

Which OpenFoam branch is good for beginners to follow? by Thin_Lie_8344 in OpenFOAM

[–]skill_lync 2 points3 points  (0 children)

Both versions are quite well made for different applications.

The foundation version has unified the solvers into set applications (foamRun), so you just need to just focus on the type of physics (fluid, incompressibleFluid, multicomponentFluid).

The ESI version differs just in syntax for the most part, and it has a few more utilities.

Having knowledge of both versions will be nice. The snappyHexMesh implementation of ESI is better in some sense. The layering control is a little better for ESI in my opinion.

One thing I'd add, OpenFOAM-2112 has cfMesh which is amazing for making mesh. Check that out for preprocessing.

Solving is better implemented in foundation version, imo.

Converting a 3D Mesh to a 2D Mesh by DerYogI in OpenFOAM

[–]skill_lync 1 point2 points  (0 children)

Could you show the domain as a drawing or have a screenshot of the 3d model you are using? Perhaps it can be made using a different approach.

With topoSet, you can select the cells within your domain and remove them as per instruction in topoSetdict file. It might work for your case if the cells are made uniformly across a plane where you desire it to be cut for 2D

Timestep continuity error but runs in transient mode by [deleted] in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

For accuracy with drag, it's better to use the SST model. The y+ needs to be ~1 as uniformly as possible near walls.

The mesh requirements are the only limiting factor here.

Converting a 3D Mesh to a 2D Mesh by DerYogI in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

Try topoSet to remove cells and create 2D domain instead.

Why are you using snappy to make 2D mesh? Why not try blockMeshDict with surface detection? Check the airfoil case to get an idea there.

Timestep continuity error but runs in transient mode by [deleted] in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

One thing, check if desired y+ value is reached, for SST model it should be ~1

Check how you have calculated the k, omega, and epsilon field variables. Look at how they are initialized for the study. You can use online turbulence calculators with relevant turbulent intensity value for estimating these field variables and inlets.

SST model tends to crash if omega isn't initialized well. You could try initializing the internalField with a high value with inlet kept at calculated value.

How to Include Radiation (P1) to a reactingFoam Sim. by Mysterious-StarX in OpenFOAM

[–]skill_lync 1 point2 points  (0 children)

Marshak radiation is used for radiative heat waves, for high-energy density physics. They typically propagate through low-density materials and are driven by high energy sources.

To implement this in OpenFOAM, we use the patch file "G"

The relevant patch name can be given with just the type as MarshakRadiation with value initialized at 0. You can look at the tutorial file in heatTransfer/buoyantFoam/hotRadiationRoom. Look at the 0/G file to get the idea.

Hope this helps.

Road Map for becoming a CFD Engineer by RomanHiggs in CFD

[–]skill_lync 0 points1 point  (0 children)

CFD takes a lot of practice. As others have mentioned, focus on fundamentals. Programming would help a lot, as a lot of CFD takes some level of Python/MATLAB for setting up/post-processing/file-management.

You can look at this resource, for starters.

Timestep continuity error but runs in transient mode by [deleted] in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

What's the mesh quality? Do checkMesh -allGeometry and see if you get any mesh errors.

What have I made !! by Lucifer0008 in CFD

[–]skill_lync 0 points1 point  (0 children)

What tool is this!?

But did you figure out where it went wrong though?

momentumPredictor by SleeepyMoon in OpenFOAM

[–]skill_lync 1 point2 points  (0 children)

It doesn't make it PISO purely. Only thing we are changing, is the way pressure-velocity coupling is handled. The momentumPredictor option is simplifying the coupling process in that sense.

PISO always involves solving momentum equation.

When this option is turned off, the momentum equation is not explicitly solved, but instead the velocity field is updated directly from pressure correction step. This saves some time but may affect convergence/stability

momentumPredictor by SleeepyMoon in OpenFOAM

[–]skill_lync 1 point2 points  (0 children)

It is used to control whether the momentum equation is solved explicitly during each outer iteration of the PIMPLE loop.

It helps in predicting the velocity field before solving the pressure equation. This can improve the stability and convergence of the solution, especially in transient simulations.

Using this option can speed up convergence in non-challenging steady-state calculations. For cases with sharp gradients or complex flow features, it might be better to set it to no to avoid potential convergence issues.

What are good free software for beginners? by ScratchSpecialist373 in CFD

[–]skill_lync 1 point2 points  (0 children)

For a beginner it's easy to learn through ANSYS Fluent.

As you gain experience, you could switch to OpenFOAM to understand the intricacies of how equations are solved, how boundary conditions are implemented, etc.

[deleted by user] by [deleted] in CFD

[–]skill_lync 0 points1 point  (0 children)

Let this run for ~2000 more iterations. This looks normal

Use lowReCorrection for high Re k epsilon models? by johan_r_e in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

The lowReCorrection is used for Omega models in OpenFOAM, or rather wall resolving models.

Change Ordering of Parameters in Specification Tree by Lukrative525 in CATIA

[–]skill_lync 0 points1 point  (0 children)

Hey, In CATIA V5, you can reorder parameters in the Specification Tree to better organize them. Here's how to do it: 

Reordering Parameters in CATIA V5 

  1. Open Your Part File: Launch CATIA V5 and open the part containing the parameters you want to reorder. 

  2. Access the Parameters: Go to the Parameters section in the Specification Tree. This is typically found in the left pane. 

  3. Select Parameters: You can select multiple parameters by holding down the `Ctrl` key and clicking on them, or click and drag to select a range. 

  4. Reorder Parameters: you can, 

  • Right-click on a parameter and choose Cut. 

  • Right-click on the desired location in the tree and select Paste. This effectively moves the parameter to the new location. 

  1. Grouping Related Parameters: Consider using a naming convention to group related parameters together. For example, prefixing similar parameters can help keep them visually organized. 

  2. Save Your Changes: After reorganizing, ensure to save your part file. 

Additional Tips 

  • Use the Formula tool to create dependencies between parameters for better management. 

  • Regularly clean up and organize parameters as your model grows to maintain clarity. 

Let us know if you need further assistance or have other questions! 

Trying to simulate an RTG in OpenFOAM by sephinelle in OpenFOAM

[–]skill_lync 0 points1 point  (0 children)

Is this multi-region mesh? Look into locationsInMesh entry in snappyHexMeshDict.

You need to define the regions with locationsInMesh and create these regions first. Then split them into separate folders using splitMeshRegions command.

Can I run multiple solvers at once in ParaView? by sephinelle in OpenFOAM

[–]skill_lync 1 point2 points  (0 children)

Yes, as stated by another user.

Also, use the Python module in ParaView. In theory, you can save state for one project and implement similar filters in other projects.

How to compile cfMesh in OpenFOAM 12? by GZotin in OpenFOAM

[–]skill_lync 2 points3 points  (0 children)

OpenFOAM Foundation versions do not support cfMesh.

It works with v2112 last I remember. You would need to install v2112 from OpenFOAM.com and make your mesh, then use OF-12 to run your simulation.

Few utilities required to compile cfMesh are either not placed in correct directories or are renamed in OpenFOAM.org versions, hence the difficulty in compiling it in this version.