Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-06-14T13:48:01Zhttps://develop.openfoam.com/Development/openfoam/-/issues/495unneeded overhead in mergePoints2017-06-14T13:48:01ZMark OLESENunneeded overhead in mergePointsVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1714unload errors for fieldfunctions library2020-06-05T14:33:34ZMark OLESENunload errors for fieldfunctions libraryThe recent changes to phase-system turbulence libraries and subsequent change to the field function link options (commit 11965904b) appear to provoke an unload error. Seen for clang (10.0), but _not_ for gcc (7.5.0).
If I do a full or ...The recent changes to phase-system turbulence libraries and subsequent change to the field function link options (commit 11965904b) appear to provoke an unload error. Seen for clang (10.0), but _not_ for gcc (7.5.0).
If I do a full or partial revert of that commit, the error shifts to being not able to load the library (double entry for "laminar" as @Pawan reported).
Here is what the error currently looks like:
```
tutorials/heatTransfer/chtMultiRegionFoam/externalCoupledHeater/
$ foamListRegions
bottomWater
topAir
heater
leftSolid
rightSolid
--> FOAM Warning :
From void Foam::dlLibraryTable::clear(bool)
in file db/dynamicLibrary/dlLibraryTable/dlLibraryTable.C at line 164
Failed closing "fieldFunctionObjects" with handle 0xa8a170
```
In the tutorial test loop this is pure poison since output (stdout) is the input for the following changeDictionary.
For additional robustness, the warnings really should be redirected to stderr when the banner is suppressed.
Additionally, loading additional libraries should likely be suppressed in `foamListRegions` as well.
This means that the errors will disappear for that tutorial, but there still seems to be fundamental issue with the field function library.
@andyv2006Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/641Unknow write type "boundaryData" in surfacesSampling format2018-05-31T09:58:47ZAdminUnknow write type "boundaryData" in surfacesSampling formatI used surfaceFormat boundaryData (A form that can be used with timeVaryingMapped boundary) in surfacesSampling to have point information.
I can still find it here :https://www.openfoam.com/documentation/user-guide/userse21.php.
In op...I used surfaceFormat boundaryData (A form that can be used with timeVaryingMapped boundary) in surfacesSampling to have point information.
I can still find it here :https://www.openfoam.com/documentation/user-guide/userse21.php.
In openFoam4.1 under Ubuntu system, "boundaryData" is a unknow type. I cannot figure it out.
Furthermore, "boundaryData" and "foamFile" don't give the same number points. The boundary conditon "timeVaryingMappedFixedValue" prefers the point file outputed from "boundaryData" which has less point number in the file than the one from "foamFile".
Best Regards,https://develop.openfoam.com/Development/openfoam/-/issues/160UNIT TESTS - 24 June2016-06-28T06:36:09ZPrashant SonakarUNIT TESTS - 24 June- tutorials/lagrangian/reactingParcelFoam/verticalChannelLTS : missing potentialFlow dict in fvSolution
- #159
@andy - tutorials/lagrangian/reactingParcelFoam/verticalChannelLTS : missing potentialFlow dict in fvSolution
- #159
@andy Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/856Unit tests: 06-06-20182018-07-02T05:02:01ZPrashant SonakarUnit tests: 06-06-2018- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/rea...- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/reactingParcelFoam/verticalChannelLTS : solver exit with maxIter 100
unconfirmed completions
- compressible/rhoSimpleFoam/gasMixing/injectorPipe: solver
cases run at /home/alex2/prashant/OpenFOAM/OpenFOAM-plus.feature-xxx/tutorialsTest
@andy @Mattijs @mark @Sergiov1806https://develop.openfoam.com/Development/openfoam/-/issues/1059Unit Test failures2019-07-03T20:14:47ZPrashant SonakarUnit Test failuresTutorials report : as of 31.10.2018
Branch: develop
```
/multiphase/interIsoFoam/damBreakWithObstacle:
log.interIsoFoam: [2] wrong token type - expected Scalar, found on line 0: word 'nan'
/multiphase/interFoam/RAS/motorBike:
...Tutorials report : as of 31.10.2018
Branch: develop
```
/multiphase/interIsoFoam/damBreakWithObstacle:
log.interIsoFoam: [2] wrong token type - expected Scalar, found on line 0: word 'nan'
/multiphase/interFoam/RAS/motorBike:
log.interFoam.restart: [0] cannot find file "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestprocessor0/0/p_rgh"
log.redistributePar.reconstruct: [4] No times selected
log.interFoam:
/multiphase/overInterDyMFoam/boatAndPropeller:
log.overInterDyMFoam:
/lagrangian/simpleReactingParcelFoam/verticalChannel:
log.simpleReactingParcelFoam: cannot find file "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestconstant/reacting1Properties"
/lagrangian/reactingParcelFoam/verticalChannelLTS:
log.reactingParcelFoam: Maximum number of iterations exceeded: 100
/mesh/parallel/filter:
log.reactingParcelFoam.parallel: [0] reactingParcelFoam: cannot open case directory "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestprocessor0"
log.redistributePar.1: [2] No times selected
log.redistributePar: [1] 'type' has 5 excess tokens in stream
/mesh/parallel/cavity:
log.redistributePar.5: [4] cannot find file "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestprocessor4/constant/polyMesh/sets/f0"
log.icoFoam.5: [3] cannot find file "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestprocessor3/0.01/p"
/mesh/snappyHexMesh/iglooWithFridgesDirectionalRefinement:
log.snappyHexMesh: [1] 'origin' not found in dictionary "/scratch/pss/351121/OpenFOAM/OpenFOAM-plus.develop/tutorialsTestsystem/snappyHexMeshDict.geometry.twoFridgeFreezers.seal.transform"
/heatTransfer/buoyantBoussinesqSimpleFoam/iglooWithFridges:
log.snappyHexMesh: cannot dereference nullptr at index 56 in range [0,3)
```
@Developmenthttps://develop.openfoam.com/Development/openfoam/-/issues/266Unify surface area/normal calculations2017-01-02T12:22:12ZMark OLESENUnify surface area/normal calculationsNeed face areas and normals for meshed surfaces in several places. It makes sense to relocate this frequently needed functionality to PrimitivePatch. PolyPatch continues to use a slice field for efficiency on poly meshes.Need face areas and normals for meshed surfaces in several places. It makes sense to relocate this frequently needed functionality to PrimitivePatch. PolyPatch continues to use a slice field for efficiency on poly meshes.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/245uniform/time dictionary searched for in all time directories2021-07-06T10:45:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/time dictionary searched for in all time directoriesAll the IOdictionaries will be searched for in all previous time instances. This is fine for e.g. polyMesh files (points, faces, etc) but wrong for e.g. uniform/time. Also it is very expensive when there are lots of time directories.
At...All the IOdictionaries will be searched for in all previous time instances. This is fine for e.g. polyMesh files (points, faces, etc) but wrong for e.g. uniform/time. Also it is very expensive when there are lots of time directories.
Attached files add some debug printing to see when it is happening (e.g. with foamToEnsight)
[IOobject.C](/uploads/e181e7fb456c4690b208304dffe67704/IOobject.C)[log.foamToEnsight](/uploads/48c62a1d1845d236c894853038e83ef7/log.foamToEnsight)https://develop.openfoam.com/Development/openfoam/-/issues/871uniform/rigidBodyMotionState dictionary cannot be re-read if running in binary2019-12-09T22:18:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/rigidBodyMotionState dictionary cannot be re-read if running in binaryMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2605uniformInterpolatedPointPatchVectorField does not work with redistributePar2022-12-23T14:56:22ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniformInterpolatedPointPatchVectorField does not work with redistributePar<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be re...<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
uniformInterpolatedPointPatchVectorField does not work with redistributePar. This is to do with the dictionary constructor forcing evaluation of the boundary condition.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Create a case with uniformInterpolatedPointPatchVectorField. Run redistributePar. It will fail with a FatalError.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2206|v2112|v2106|v2012|v2006 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2206
- Operating system :
- Hardware info :
- Compiler :
### Possible fixes
<!--
If you can, link to the line of code that might be responsible for the
problem
The "/label ~bug" text is a gitlab flag that will add the "bug" label to this
issue
-->
Delay searching for times until they are actually needed.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2uniformInletOutletFvPatchField uniform value is not being updated2023-08-19T21:13:18ZAdminuniformInletOutletFvPatchField uniform value is not being updatedThe condition uses a DataEntry<Type> to define the uniform value, and this is not being updated in the call to updateCoeffs()The condition uses a DataEntry<Type> to define the uniform value, and this is not being updated in the call to updateCoeffs()Functionality migration from internal development lineAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/158uniform/functionObjects/functionObjectProperties gets written even if no func...2020-01-03T09:58:37ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/functionObjects/functionObjectProperties gets written even if no functionObjectsE.g. icoFoam/cavity case
E.g. icoFoam/cavity case
Version v1612https://develop.openfoam.com/Development/openfoam/-/issues/1058uniformFixedValue bc cannot be used in second order cases (restart)2018-12-24T09:00:22ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniformFixedValue bc cannot be used in second order cases (restart)@Development
uniformFixedValue bc
- never reads the 'value' field
- never maps the value
and instead re-evaluates the Function1. This is wrong for old-time fields ('_0'). Try e.g. compressible/rhoPimpleFoam/laminar/sineWaveDamping with...@Development
uniformFixedValue bc
- never reads the 'value' field
- never maps the value
and instead re-evaluates the Function1. This is wrong for old-time fields ('_0'). Try e.g. compressible/rhoPimpleFoam/laminar/sineWaveDamping with for 0/p
```
type uniformFixedValue; // oscillatingFixedValue;
uniformValue table ((0 100000)(1 200000));
```
run for a bit and then decompose a time with p_0.https://develop.openfoam.com/Development/openfoam/-/issues/2313Understanding the Darwin section of the etc/config.sh/settings2021-12-22T12:19:11ZFoadUnderstanding the Darwin section of the etc/config.sh/settingsThis is actually not an issue, more of a question leading towards a possible enhancement.
running the `source <path>/etc/bashrc` command on macOS returns the
> openfoam: darwin support is clang/llvm only
error message, coming from t...This is actually not an issue, more of a question leading towards a possible enhancement.
running the `source <path>/etc/bashrc` command on macOS returns the
> openfoam: darwin support is clang/llvm only
error message, coming from the `etc/config.sh/settings` bash script:
~~~bash
Darwin)
WM_ARCH=darwin64
[ "$WM_COMPILER" = Gcc ] && WM_COMPILER=Clang
echo "openfoam: darwin support is clang/llvm only" 1>&2
;;
~~~
Now I am not quite sure what this code block is supposed to do. I also tried to search the code-base for the `WM_COMPILER` variable to see where it has been set.
On my machine, I have several compilers including
- Apple's XCode `/usr/bin/clang`
<pre>
Apple clang version 12.0.5 (clang-1205.0.22.9)
Target: x86_64-apple-darwin21.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
</pre>
- GNU Gcc `/usr/local/Cellar/gcc/11.1.0_1/bin/gcc-11`
<pre>
gcc-11 (Homebrew GCC 11.1.0_1) 11.1.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
</pre>
ideally, I would like to choose the compiler set by providing arguments to the `<path>/etc/bashrc` script.https://develop.openfoam.com/Development/openfoam/-/issues/1079Under-resolved sampling utility2021-07-06T13:51:04ZAdminUnder-resolved sampling utilityHi!
I used the command "postProccess -func singleGraph" to extract the boundary layer in a simple lid-driven cavity case with turbulence modeling and a mesh that resolves the boundary layer (y+ of the order of 1). The extracted point cl...Hi!
I used the command "postProccess -func singleGraph" to extract the boundary layer in a simple lid-driven cavity case with turbulence modeling and a mesh that resolves the boundary layer (y+ of the order of 1). The extracted point clearly missed the near-wall region. I resolved this issue by changing the tolerance in the file $FOAM_SRC/sampling/sampledSet/face/faceOnlySet.C on line 40 to 1e-12. The original line is:
const scalar faceOnlySet::tol = 1e-6;
Therefore, I suggest to modify this value. Perhaps using the SMALL macro would be appropriate? Otherwise, allowing user modification with a lookupOrDefault statement would be nice.
Best regards,
Mathieu Olivier
Université Laval
\#\# Reattaching the author to the issue ticket: @mathieu \#\#https://develop.openfoam.com/Development/openfoam/-/issues/559unbounded volume fraction for floatingBody example2019-01-08T15:41:26ZAdminunbounded volume fraction for floatingBody exampleI am playing with floatingBody tutorial to test the overset functionality.
At first, I set up a drop test by modifying the initial position of the floating body.
It looked good.
So, next I rotated the body by 35 deg to simulate a lifeboa...I am playing with floatingBody tutorial to test the overset functionality.
At first, I set up a drop test by modifying the initial position of the floating body.
It looked good.
So, next I rotated the body by 35 deg to simulate a lifeboat drop test. the attached file is the case for this simulation. the simulation did not work on the impact of interface about 0.52 sec.
I checked fields and found the volume fraction went up above 1 (max is above 800) and the phases went upside-down. I spent several days to resolve this behavior but failed.
It would be gratefull if somebody guide me what should be corrected.
Also, is there a way to impose initial velocity and angular velocity to the floating body?
Thanks in advance.
[inclinedDrop.tar.bz2](/uploads/a69e1d43eba9a5e205e0441c1df28365/inclinedDrop.tar.bz2)https://develop.openfoam.com/Development/openfoam/-/issues/297unallocated list in triSurface vtk reader (non-critical)2016-12-15T21:07:15ZMark OLESENunallocated list in triSurface vtk reader (non-critical)Condition is there to catch cases where the vtkSurfaceFormat returns 0 zones (which should never be the case), but assigns a fall-back value without resizing the list first.Condition is there to catch cases where the vtkSurfaceFormat returns 0 zones (which should never be the case), but assigns a fall-back value without resizing the list first.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2462Unable to set source and target faces (coupled boundary condition)2022-05-09T12:25:38ZSunag R AUnable to set source and target faces (coupled boundary condition)
### Summary
Hi,
I am trying to work on patch to patch coupled boundary condition. I came across coupled boundary condition namely AMI, CyclicAMI. I am new to this part.
1. Does AMI and CyclicAMI work only for dynamic meshes?
2. I am ...
### Summary
Hi,
I am trying to work on patch to patch coupled boundary condition. I came across coupled boundary condition namely AMI, CyclicAMI. I am new to this part.
1. Does AMI and CyclicAMI work only for dynamic meshes?
2. I am trying to interpolate the dirichlet boundary conditon values on one patch to adjacent patch using AMI boundary condition. (The mesh does not move and still I have tried to use it).
3. I am facing an issue stating as mentioned in title as "Unable to set source and target faces".
My boundary file is as follows as present in constant/polymesh/boundary:
```
3
(
AMI_patch1
{
type cyclicAMI;
inGroups 1(cyclicAMI);
matchTolerance 0.001;
transform noOrdering;
neighbourPatch AMI_patch2;
nFaces 7113;
startFace 730746;
separationVector (0.005 0 0);
}
chestwall
{
type patch;
nFaces 5196;
startFace 737859;
}
AMI_patch2
{
type cyclicAMI;
inGroups 1(cyclicAMI);
matchTolerance 0.001;
transform noOrdering;
neighbourParch AMI_patch1;
nFaces 9334;
startFace 743055;
separationVector (-0.005 0 0);
}
)
```
I am working with chtMultiRegionSimpleFoam, due to this, the region boundary corresponding to the AMI patches are also same.
### What is the current *bug* behaviour?
Error:
```
AMI: Creating addressing and weights between 7113 source faces and 9334 target faces
--> FOAM Warning :
From function void Foam::AMIMethod<SourcePatch, TargetPatch>::checkPatches() const [with SourcePatch = Foam::PrimitivePatch<Foam::face, Foam::SubList, const Foam::Field<Foam::Vector<double> >&>; TargetPatch = Foam::PrimitivePatch<Foam::face, Foam::SubList, const Foam::Field<Foam::Vector<double> >&>]
in file lnInclude/AMIMethod.C at line 57
Source and target patch bounding boxes are not similar
source box span : (0.163847 0.1670128 0.08645282)
target box span : (0.2068839 0.1798336 0.08224967)
source box : (0.003686016 -0.0002872496 0) (0.167533 0.1667256 0.08645282)
target box : (0.07743542 -0.006471181 0) (0.2843193 0.1733624 0.08224967)
inflated target box : (0.0631258 -0.0207808 -0.01430962) (0.2986289 0.187672 0.09655929)
--> FOAM FATAL ERROR:
Unable to set source and target faces
From function void Foam::faceAreaWeightAMI<SourcePatch, TargetPatch>::setNextFaces(Foam::label&, Foam::label&, Foam::label&, const boolList&, Foam::labelList&, const Foam::DynamicList<int>&, bool) const [with SourcePatch = Foam::PrimitivePatch<Foam::face, Foam::SubList, const Foam::Field<Foam::Vector<double> >&>; TargetPatch = Foam::PrimitivePatch<Foam::face, Foam::SubList, const Foam::Field<Foam::Vector<double> >&>; Foam::label = int; Foam::boolList = Foam::List<bool>; Foam::labelList = Foam::List<int>]
in file lnInclude/faceAreaWeightAMI.C at line 287.
FOAM aborting
```
### What is the expected *correct* behavior?
I need to have patch to patch interpolated field flow after each iteration.
### Other
How does this AMI work and what are the changes need to be made.? For reference, I have attached the surface image for reference, where the left patch contains the dirichlet boundary condition and right patch is the one where the interpolation from dirichlet boundary condition showed happen.
Is there a possibility of interpolating one surface patch to another for a static mesh? Open to give the case files.
![image_ami](/uploads/6472a2d08f85017de34a835c747b8df3/image_ami.png)
### Environment information
- OpenFOAM version : 5
- Operating system : Ubuntu 18.04.6 LTShttps://develop.openfoam.com/Development/openfoam/-/issues/2140Unable to run flowover cylinder tutorial in potentialFoam using Allrun2021-06-25T18:40:16ZAshutosh MauryaUnable to run flowover cylinder tutorial in potentialFoam using AllrunI tried to run flow over Cylinder using Allrun this giving me error (more in log file attached). This Issue similar to my previous issue.
OpenFoam Version: 2012
OS: Ubuntu 20.04 on WSL
Compiler : 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
...I tried to run flow over Cylinder using Allrun this giving me error (more in log file attached). This Issue similar to my previous issue.
OpenFoam Version: 2012
OS: Ubuntu 20.04 on WSL
Compiler : 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
[log.potentialFoam](/uploads/30b1885ece4619ef3439642a5812b67a/log.potentialFoam)Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2759Unable to install openfoam2023-04-14T10:32:47ZSaurav ChaudhariUnable to install openfoamI am unable to install OpenFOAM CFD Module on my Windows. It's showing some error at line 47.
![OpenFOAM](/uploads/ef7b5578c108aa4ca39db7c73fac4c7f/OpenFOAM.jpg)I am unable to install OpenFOAM CFD Module on my Windows. It's showing some error at line 47.
![OpenFOAM](/uploads/ef7b5578c108aa4ca39db7c73fac4c7f/OpenFOAM.jpg)