Development issueshttps://develop.openfoam.com/groups/Development/-/issues2020-06-19T14:44:16Zhttps://develop.openfoam.com/Development/openfoam/-/issues/845handle double-dashed options2020-06-19T14:44:16ZMark OLESENhandle double-dashed optionsCan be useful when writing utilities that should mimic standard system utilities with `--option` conventions. Somewhat misleading, however, since the single-dash does not correspond to short option with bundling.
Note, in addition to equ...Can be useful when writing utilities that should mimic standard system utilities with `--option` conventions. Somewhat misleading, however, since the single-dash does not correspond to short option with bundling.
Note, in addition to equal treatment for single or double dashes, should also support `=` for option separation. For example,
decomposePar --decomposeParDict=system/mydecompDict
@andyMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/80ENH: Add a warning/error message for 2D case for solidBodyMotion in thickness...2021-07-06T10:32:56ZPrashant SonakarENH: Add a warning/error message for 2D case for solidBodyMotion in thickness directionPlaceholder for development:
If the case has non-aligned edges (or develop such situation through motion), user must be warned.
@andyPlaceholder for development:
If the case has non-aligned edges (or develop such situation through motion), user must be warned.
@andyMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/95is interFOAM restricted to certain length scales?2016-05-02T19:14:37ZAdminis interFOAM restricted to certain length scales?Hi Foam devs;
This is my 1st report and hope you guys help me out. I report this issue as I found nothing really related to this issue nor anyone could answer me in CFD online!!
I use interFOAM solver and using capillary-rise tutori...Hi Foam devs;
This is my 1st report and hope you guys help me out. I report this issue as I found nothing really related to this issue nor anyone could answer me in CFD online!!
I use interFOAM solver and using capillary-rise tutorial.
My problem is related to 2D usage of the capillary tube with an "empty" boundary condition. (I use g = 0m/s2).
I deal with micro-channels. So, I am usually dealing with length scales of 1e-6m and below.
As I understand from "empty" b.c. "nothing (no computation)" is being done along the empty dimension. What happens along other 2 axis is projected along the 3rd dimension.
As you see in the attached word doc, I performed several test cases over different length scales of the capillary tube and I see a severely diffused interface when I change my 3rd dimension. {Or to be more specific when the cross sectional area of the capillary tube is below 2e-10 m2}. Being an empty b.c., I would not expect this behavior and would expect a sharp interface for any value used in the 3rd dimension. Is there a limit based on length scales (or cross-sectional area of capillary) to which we can use interFoam? Important to mention that I tried even with a very small time step as well with no improvement of behavior. Also checked the case with a compression factor of 4 and grid refinement. Still the problem exists.
Really interested to know why this behavior is seen. As an example also attached a test case where the interface is getting diffused.
[interface_report..docx](/uploads/bdeb311b8168b6081f8e1bbc009aa8ee/interface_report..docx)
[interfaceSmaring3BbNum1we-8.zip](/uploads/2fa2df3583ff9dedd9a7180ffaed7fc2/interfaceSmaring3BbNum1we-8.zip)
Thanks and best;
SaideepSergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/915paraFoam starts up with 'Skip 0/ time' enabled2020-03-13T14:42:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaFoam starts up with 'Skip 0/ time' enabled1) Do we still need this?
2) Why do we only select p,U,T and not all fields?1) Do we still need this?
2) Why do we only select p,U,T and not all fields?https://develop.openfoam.com/Development/openfoam/-/issues/347surfaceCheck - no outputThreshold option2017-12-22T15:34:47ZMatej FormansurfaceCheck - no outputThreshold optionThe source code of surfaceCheck lists the -outputThreshold option, but the utility is not compiled with the option available.
surfaceCheck returns: Invalid option: -outputThreshold
(both master and develop trees)The source code of surfaceCheck lists the -outputThreshold option, but the utility is not compiled with the option available.
surfaceCheck returns: Invalid option: -outputThreshold
(both master and develop trees)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/787forceCoeff writeFields option producing strange values: areaIntegrate of forc...2020-11-07T16:15:14ZAdminforceCoeff writeFields option producing strange values: areaIntegrate of forceCoeff field != forceCoeffI have been using the forceCoeffs function object for a long time, and am trying the writeFields option in v1712. However, it produces very strange values. I have a test case with one wall patch, and from the solving log, I can see that ...I have been using the forceCoeffs function object for a long time, and am trying the writeFields option in v1712. However, it produces very strange values. I have a test case with one wall patch, and from the solving log, I can see that the forceCoeff for that patch is quite different from the areaIntegrate of forcesAll:forceCoeff on that patch. I would expect the integral to give a value close to Cd pressure+viscous.
When I plot contours of forcesAll:forceCoeff in paraview, I see very low max values (~0.0002), when I should see surface normal*Cp, and Cp is roughly between -2 and 1.
I can supply a solved test case, and the relevant /system files and log files are attached.
```
forceCoeffs forcesAll execute:
Coefficients
Cm : -239.9753 (pressure: 176.0671 viscous: 0.6762368 porous: -416.7187)
Cd : 2.021964 (pressure: 1.242636 viscous: 0.005935802 porous: 0.7733919)
Cl : 2.230875 (pressure: 0.2968915 viscous: 0.001180773 porous: 1.932802)
Cl(f) : -238.8599
Cl(r) : 241.0908
surfaceFieldValue surfaceFieldValue1 write:
total area = 2.59955
areaNormalIntegrate(wall_l_body) of forcesAll:forceCoeff = (-0.0001750436 0 0)
surfaceFieldValue surfaceFieldValue2 write:
total area = 2.59955
areaIntegrate(wall_l_body) of forcesAll:forceCoeff = (9.107523e-05 -9.712166e-06 2.222456e-05)
```
[forcesAll](/uploads/3e40a39f7e41c19ceb9658ac4428ec60/forcesAll)
[controlDict](/uploads/bba6ee01fbd6897c829fa71d341de1e7/controlDict)[log.solve_OF.log](/uploads/19fd0116aeba1926522729982229ff92/log.solve_OF.log)
\#\# Reattaching the author to the issue ticket: @aerogt3 \#\#Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/301update errors occur2016-11-29T16:01:24ZAdminupdate errors occurToday update errors occur in [foamToEnsight], [dataConversion] and [postProcessing].
I don't solve these errors.
[log.make-14.tar.gz](/uploads/48093b3461ce9de509a3259499546819/log.make-14.tar.gz)
---
Using: OpenFOAM-plus (see www.Ope...Today update errors occur in [foamToEnsight], [dataConversion] and [postProcessing].
I don't solve these errors.
[log.make-14.tar.gz](/uploads/48093b3461ce9de509a3259499546819/log.make-14.tar.gz)
---
Using: OpenFOAM-plus (see www.OpenFOAM.com)
Build: plus-73c5bd603f2cMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/249Field construct from indirect list2016-10-04T09:50:10ZMark OLESENField construct from indirect listCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/675Failures - collate fileHandler - 20.12.20172023-12-22T09:19:14ZPrashant SonakarFailures - collate fileHandler - 20.12.2017Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3line...Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3lines.txt)
- list of unconfirmed completions. [listOfUnconfirmedCompletion.txt](/uploads/4e87a9784b7354cd00da7cdc77cdfe83/listOfUnconfirmedCompletion.txt)
run with $FOAM_ETC/controlDict set to collated in
/hosts/punwor073/home/pss/OpenFOAM/compilations/ALPHA/centos6.6_compilation/OpenFOAM-plus.develop/tutorialsTest
@Mattijs @mark @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/113BUG/ENH: incomplete installtion check with foamInstallationTest2017-03-16T08:30:19ZPrashant SonakarBUG/ENH: incomplete installtion check with foamInstallationTestThe utility performs check for basic installation and confirms success.
However if some of the dependencies are not resolved (e.g. CGAL, boost,...) few utilities will not be installed (e.g. surfaceFeatureExtract, snappyHexMesh,...) bu...The utility performs check for basic installation and confirms success.
However if some of the dependencies are not resolved (e.g. CGAL, boost,...) few utilities will not be installed (e.g. surfaceFeatureExtract, snappyHexMesh,...) but rest would be OK
I think foamInstallationTest should check overall picture and report
- missing dependencies (including any third-party)
- failed libraries/applications
etc...
@Mattijs
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/402BUG: noise with -case and/or -dict option2019-12-09T21:29:27ZPrashant SonakarBUG: noise with -case and/or -dict optionThe input files read from the noiseDict must be absolute path or using environment variables like $FOAM_CASE
The relative path doesn't work.[Test_innerPath.tgz](/uploads/24d7858f28fe9f6cf4b7201d2438c654/Test_innerPath.tgz)
Ref: EP#338The input files read from the noiseDict must be absolute path or using environment variables like $FOAM_CASE
The relative path doesn't work.[Test_innerPath.tgz](/uploads/24d7858f28fe9f6cf4b7201d2438c654/Test_innerPath.tgz)
Ref: EP#338AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/658Feature: Possibility for Regular Expressions in snappyHexMeshDict, surfaceFea...2020-01-03T14:31:23ZKutalmış BerçinFeature: Possibility for Regular Expressions in snappyHexMeshDict, surfaceFeatureExtractDict etc. for File NamesA user is able to use POSIX regular expressions for OpenFOAM's **keywords** as well as **file names** for *some* entries: such as `refinementSurfaces` and `refinementRegions` entries in a `snappyHexMeshDict` as exemplified herein: https:...A user is able to use POSIX regular expressions for OpenFOAM's **keywords** as well as **file names** for *some* entries: such as `refinementSurfaces` and `refinementRegions` entries in a `snappyHexMeshDict` as exemplified herein: https://bugs.openfoam.org/view.php?id=527
Yet one currently cannot use this flexibility for **file names** in `surfaceFeatureExtractDict` and `geometry` entry of a `snappyHexMeshDict`. Might be useful to expand the above for the latter, I believe.
Kind regardsKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/837PackedBoolList/bitSet has no ::set(const labelUList&)2018-06-07T05:57:54ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comPackedBoolList/bitSet has no ::set(const labelUList&)This has been renamed to 'setMany'. Is there a problem with ::set? Is there a clear distinction with single element setting?This has been renamed to 'setMany'. Is there a problem with ::set? Is there a clear distinction with single element setting?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/709blended factor is written every time step2018-01-29T09:06:06Zvilfayeaublended factor is written every time stepHi,
When using
```
DebugSwitches
{
blendedSchemeBase 1;
}
```
The blended factor is printed every timestep instead of writeControl/Interval.
Best,
SebastienHi,
When using
```
DebugSwitches
{
blendedSchemeBase 1;
}
```
The blended factor is printed every timestep instead of writeControl/Interval.
Best,
Sebastienhttps://develop.openfoam.com/Development/openfoam/-/issues/782Problem in mean temperature and mean compressibility calculation in thermophy...2021-07-08T12:23:53ZAdminProblem in mean temperature and mean compressibility calculation in thermophysical library for premixed flameHello
The calculation of mean temeperature and mean compressibility i.e. T and psi, in the thermophysical library for a premixed turbulent flame has been problematic since an earlier version of OpenFOAM-v1.6. Please find the attached p...Hello
The calculation of mean temeperature and mean compressibility i.e. T and psi, in the thermophysical library for a premixed turbulent flame has been problematic since an earlier version of OpenFOAM-v1.6. Please find the attached pdf file for a detailed description. The latestest OpenFOAM-v1712 has the same problem.
The relavant code is $WM_PROJECT_DIR/src/thermophysicalModels/reactionThermo/psiuReactionThermo/heheuPsiThermo.C
in which the member function of calculation() calculates the mean temperatrue and compressibility psi.
Moreover, it is misleading to consider regress progress variable "b" in solver XiFoam as a mass fraction of some products in the premixed flame as implemented in OpenFOAM; see code $WM_PROJECT_DIR/src/thermophysicalModels/reactionThermo/mixtures/homogeneousMixture/homogeneousMixture.C.
The reason is that the regress progress variable "b" is based on the Bray-Mossy-Libby model of premixed flame in which the unburned and burned mixture is seperated by a infinitely thin flame front. The "b" has a physical meaning of probability of finding the unburned mixture, not some mass fraction.
I hope that I managed to explain the problem, otherwise please contact me if there is anything unclear.
Kind regards
Chen[ehsan_yasari_ab.pdf](/uploads/fe7807d8e465f774ff8b134d5ea0561b/ehsan_yasari_ab.pdf)
\#\# Reattaching the author to the issue ticket: @chenhu \#\#Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/843libFieldFunctionObjects writeInterval2018-06-01T13:04:49ZAdminlibFieldFunctionObjects writeIntervalIn the v1712 release the following libFieldFunctionObjects
dummy
{
type wallShearStress;
libs ("libfieldFunctionObjects.so")
writeControl timeStep;
writeInterval 1e+06;
writeFiel...In the v1712 release the following libFieldFunctionObjects
dummy
{
type wallShearStress;
libs ("libfieldFunctionObjects.so")
writeControl timeStep;
writeInterval 1e+06;
writeFields no;
patches ("board.*");
log no;
}
writes the wallShearStress field in the case directory every time step. The same controlDict sintax worked fine for the same case with the 2.4.0 version, with the field object written every specified write interval (using outputInterval in the old version).https://develop.openfoam.com/Development/openfoam/-/issues/783surfaceFieldValue does not check for failure to open data file2023-12-07T19:03:27ZPrashant SonakarsurfaceFieldValue does not check for failure to open data fileWith >1024 surfaceFieldValue function objects you might run out of filedescriptors for the data file!
There is currently no error message if it cannot open a data file.With >1024 surfaceFieldValue function objects you might run out of filedescriptors for the data file!
There is currently no error message if it cannot open a data file.Prashant SonakarPrashant Sonakarhttps://develop.openfoam.com/Development/openfoam/-/issues/655UOPstream does not zero padding (placeholder)2021-07-06T11:31:22ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comUOPstream does not zero padding (placeholder)UOPstream enforces alignment of individual blocks. It does not fill the added padding with zero. This shows up when running e.g. valgrind.
- Not a bug since we also don't read the padded data.
- Avoid by using setSize(xxx, 0) instead of...UOPstream enforces alignment of individual blocks. It does not fill the added padding with zero. This shows up when running e.g. valgrind.
- Not a bug since we also don't read the padded data.
- Avoid by using setSize(xxx, 0) instead of setSize(xxx)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/381mergePatchFaces in multiphase/interDyMFoam/RAS/motorBike2018-05-29T05:39:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commergePatchFaces in multiphase/interDyMFoam/RAS/motorBikeMerging patch faces is switched on in the tutorial. It makes more sense to switch it on.Merging patch faces is switched on in the tutorial. It makes more sense to switch it on.https://develop.openfoam.com/Development/openfoam/-/issues/1238add support for mingw cross-compilation2020-08-05T17:56:26ZMark OLESENadd support for mingw cross-compilationMark OLESENMark OLESEN