Development issueshttps://develop.openfoam.com/groups/Development/-/issues2023-12-07T19:02:00Zhttps://develop.openfoam.com/Development/openfoam/-/issues/153BUG: fixedMean BC "unallocated"2023-12-07T19:02:00ZPrashant SonakarBUG: fixedMean BC "unallocated"Attached case illustrates the bug in develop branch.
[pitzDaily_fixedMean.tgz](/uploads/500c361b6a284a1297e6c9d2a6a12298/pitzDaily_fixedMean.tgz)
It is when included file defines the value for meanValue entry.
```
Constructin...Attached case illustrates the bug in develop branch.
[pitzDaily_fixedMean.tgz](/uploads/500c361b6a284a1297e6c9d2a6a12298/pitzDaily_fixedMean.tgz)
It is when included file defines the value for meanValue entry.
```
Constructing velocity potential field Phi
No MRF models present
Calculating potential flow
--> FOAM FATAL ERROR:
object of type N4Foam9Function1IdEE is not allocated
From function T* Foam::autoPtr<T>::operator->() [with T = Foam::Function1<double>]
in file /xxx/OpenFOAM-plus.develop/src/OpenFOAM/lnInclude/autoPtrI.H at line 176.
FOAM aborting
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::error::abort() at ??:?
#2 Foam::fixedMeanFvPatchField<double>::updateCoeffs() at ??:?
#3 Foam::fvMatrix<double>::fvMatrix(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::dimensionSet const&) at ??:?
#4 Foam::fv::gaussLaplacianScheme<double, double>::fvmLaplacianUncorrected(Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
#5 Foam::fv::gaussLaplacianScheme<double, double>::fvmLaplacian(Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
#6 Foam::tmp<Foam::fvMatrix<double> > Foam::fvm::laplacian<double, double>(Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::word const&) at ??:?
#7 ? at ??:?
#8 ? at ??:?
#9 __libc_start_main in "/lib64/libc.so.6"
#10 ? at ??:?
```
@Sergio @Mattijs AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/480pointConstraints don't handle coupled points on inside of patch2017-06-29T20:38:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.compointConstraints don't handle coupled points on inside of patchThe constraint mechanism (for point motion) assumes that all coupled points are on the outside of 'normal' patches. Very occasionally this is not the case and it causes out-of-bounds access to the list of constraints (patchPatchPointCons...The constraint mechanism (for point motion) assumes that all coupled points are on the outside of 'normal' patches. Very occasionally this is not the case and it causes out-of-bounds access to the list of constraints (patchPatchPointConstraints_)Version v1706https://develop.openfoam.com/Development/openfoam/-/issues/1073change internal dictionary separator2024-01-10T19:58:42ZMark OLESENchange internal dictionary separatorPropose for **1906**, we could adjust the internal dictionary separator from a dot (.) to a comma (,) separator.
The change in output appearance would be minimal. Eg,
```
/path/dictionary/subdict1,subdict2,entry
```
But by using a comma,...Propose for **1906**, we could adjust the internal dictionary separator from a dot (.) to a comma (,) separator.
The change in output appearance would be minimal. Eg,
```
/path/dictionary/subdict1,subdict2,entry
```
But by using a comma, which is rarely if ever used within a keyword, we could have things like this
```
file.obj
{
type xxx;
}
```
And now be able to recover the keyword `file.obj` from the dictionary dictName() method. At the moment the dictName() parses based on dot and would return `obj` instead.
@Developmentv1906Mark OLESENMark OLESEN2019-02-01https://develop.openfoam.com/Development/openfoam/-/issues/156snappyHexMesh failure for pipe_snapAtInterface2023-12-07T19:02:01ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh failure for pipe_snapAtInterfaceFails to assign all cells to a cellZone or -1; leaves them -2 which causes problems.
/home/alex2/prashant/QA/UNIT_TESTS/OpenFOAM-test.merge-foundation-test2/testCases/mesh/pipe_snapAtInterfaceFails to assign all cells to a cellZone or -1; leaves them -2 which causes problems.
/home/alex2/prashant/QA/UNIT_TESTS/OpenFOAM-test.merge-foundation-test2/testCases/mesh/pipe_snapAtInterfaceMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/175Compile error occurs! ( -plus _v1606+)2017-01-26T15:22:26ZAdminCompile error occurs! ( -plus _v1606+)Today, I tried to install of-plus (v1606+) but failed it.
A part of the error messages are the following.
---
...
fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C:1110:63: error: no matching fu...Today, I tried to install of-plus (v1606+) but failed it.
A part of the error messages are the following.
---
...
fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C:1110:63: error: no matching function for call to ‘Foam::turbulentDFSEMInletFvPatchVectorField::writeEntryIfDifferent(Foam::Ostream&, const char [13], int, const label&) const’
writeEntryIfDifferent(os, "nCellPerEddy", 5, nCellPerEddy_);
^
fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C:1110:63: note: candidate is:
In file included from lnInclude/fixedValueFvPatchField.H:58:0,
from lnInclude/fixedValueFvPatchFields.H:29,
from fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.H:83,
from fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C:26:
lnInclude/fvPatchField.H:533:18: note: template<class EntryType> void Foam::fvPatchField<Type>::writeEntryIfDifferent(Foam::Ostream&, const Foam::word&, const EntryType&, const EntryType&) const [with EntryType = EntryType; Type = Foam::Vector<double>]
void writeEntryIfDifferent
^
lnInclude/fvPatchField.H:533:18: note: template argument deduction/substitution failed:
fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C:1110:63: note: deduced conflicting types for parameter ‘const EntryType’ (‘int’ and ‘Foam::label {aka long int}’)
writeEntryIfDifferent(os, "nCellPerEddy", 5, nCellPerEddy_);
...
----
What should I do next?
[make.log-1.zip](/uploads/b021a7fd041552b1271b91555f6f0c86/make.log-1.zip)Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/326ENH: wmake for file with future timestamp2021-07-06T11:04:27ZPrashant SonakarENH: wmake for file with future timestampPlaceholder for check for files with future time stamp (when transferred between different systems)Placeholder for check for files with future time stamp (when transferred between different systems)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/214Typo in 'SunDirTraking'2016-09-28T17:27:10ZAdminTypo in 'SunDirTraking'This is by no means critical, but `SunDirTraking` has a typo, since it's missing the `c` in `Tracking`, i.e. it should be `SunDirTracking`.
The files that have these typos can be found with the following commands:
```
grep -r 'Sun...This is by no means critical, but `SunDirTraking` has a typo, since it's missing the `c` in `Tracking`, i.e. it should be `SunDirTracking`.
The files that have these typos can be found with the following commands:
```
grep -r 'SunDirTraking' applications src tutorials
grep -r 'sunDirTraking' applications src tutorials
```
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/14Documentation/Bug: ID 27: SHM- avoid mesh distorsion in far field2023-08-19T21:13:19ZPrashant SonakarDocumentation/Bug: ID 27: SHM- avoid mesh distorsion in far fieldIs pointSmoother ($FOAM_SRC/dynamicMesh/pointSmoothers) integrated yet?
The example for this feature is mentioned as incompressible/simpleFoam/motorBike??
@andy Is pointSmoother ($FOAM_SRC/dynamicMesh/pointSmoothers) integrated yet?
The example for this feature is mentioned as incompressible/simpleFoam/motorBike??
@andy Functionality migration from internal development lineMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/861residual FO : DebugInfo2018-07-04T10:44:48ZPrashant Sonakarresidual FO : DebugInfoIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @MattijsIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @Mattijsv1806https://develop.openfoam.com/Development/openfoam/-/issues/752Feature: Writing mesh quality fields under a separate directory2021-10-20T12:59:50ZKutalmış BerçinFeature: Writing mesh quality fields under a separate directoryHi,
Please consider the following command within a case directory:
`checkMesh -writeAllFields`
If `0` directory exists, `8(cellDeterminant nonOrthoAngle cellVolumeRatio skewness faceWeight aspectRatio cellVolume cellShapes)` field fil...Hi,
Please consider the following command within a case directory:
`checkMesh -writeAllFields`
If `0` directory exists, `8(cellDeterminant nonOrthoAngle cellVolumeRatio skewness faceWeight aspectRatio cellVolume cellShapes)` field files are written under `0` directory, otherwise under `constant` directory.
There might be times for a user who may find this conceptually and practically messy.
IMHO, collecting these fields under a directory may be useful in terms of tidiness.
Kind regardshttps://develop.openfoam.com/Development/openfoam/-/issues/1068COMP: issue in executables getting segmentFault2018-11-13T09:48:23ZPrashant SonakarCOMP: issue in executables getting segmentFaultWith latest develop pulled today, the compilations runs through OK.
However none of the executable work. All end up with segment Fault.
Changing the file src/OpenFOAM/fields/Fields/fieldTypes.C
```
const Foam::wordList Foam::fieldTypes...With latest develop pulled today, the compilations runs through OK.
However none of the executable work. All end up with segment Fault.
Changing the file src/OpenFOAM/fields/Fields/fieldTypes.C
```
const Foam::wordList Foam::fieldTypes::basic
({
"labelField", //Foam::labelIOField::typeName,
"scalarField", //Foam::scalarIOField::typeName,
"vectorField", //Foam::vectorIOField::typeName,
"sphericalTensorField", //Foam::sphericalTensorIOField::typeName,
"symmTensorField", //Foam::symmTensorIOField::typeName,
"tensorField" //Foam::tensorIOField::typeName
});
```
seems to work.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/602redistributePar -reconstruct produces different phi field w.r.t. reconstructPar2024-01-10T16:22:29ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar -reconstruct produces different phi field w.r.t. reconstructPar- take parallel/filter tutorial
- reconstruct time 0.8 (using ascii, 16 digits writeprecision) with both
```
reconstructPar -time 0.8
mpirun -np 3 redistributePar -reconstruct -time 0.8
```
The phi field differs in the last digits on som...- take parallel/filter tutorial
- reconstruct time 0.8 (using ascii, 16 digits writeprecision) with both
```
reconstructPar -time 0.8
mpirun -np 3 redistributePar -reconstruct -time 0.8
```
The phi field differs in the last digits on some faces.https://develop.openfoam.com/Development/openfoam/-/issues/1246minor issue: pressureDifference.cfg2019-12-09T22:37:28ZAdminminor issue: pressureDifference.cfgThere is a semi colon missing after the line
writeInterval 1
in
etc/caseDicts/postProcessing/pressure/pressureDifference.cfgThere is a semi colon missing after the line
writeInterval 1
in
etc/caseDicts/postProcessing/pressure/pressureDifference.cfgMark OLESENMark OLESENhttps://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/130ENH: Extend the foamSystemCheck to include dependencies2017-03-16T08:30:39ZPrashant SonakarENH: Extend the foamSystemCheck to include dependenciesIt might be good to simply execute a script to check any missing dependencies than stating long list in release note.
It would also help non-IT expert to know the missing items.
e.g. flex, bison, cmake, zlib etc could be added to t...It might be good to simply execute a script to check any missing dependencies than stating long list in release note.
It would also help non-IT expert to know the missing items.
e.g. flex, bison, cmake, zlib etc could be added to this system test.
This should assist installation by also listing dependencies required in ThirdParty folder (if any)
@wyldckat @Mattijs @mark @Pawan AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/714ENH: bounds for plane sampling2023-12-07T19:03:27ZPrashant SonakarENH: bounds for plane samplingIf bounds provided have a common co-ordinate (squeezed box), it doesn't warn.
- add a warning
@mark @Mattijs
cross ref: EP#519If bounds provided have a common co-ordinate (squeezed box), it doesn't warn.
- add a warning
@mark @Mattijs
cross ref: EP#519Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/67BUG : compile on debian jessie2017-03-16T05:53:27ZAdminBUG : compile on debian jessieI must modify the "whichmpi" variable in the file OpenFOAM-v3.0+/src/Pstream/Allwmake in order to compile Openfoam-v3.0+
initial v3.0+ variable :
whichmpi="$WM_PROJECT_DIR/platforms/$WM_OPTIONS/src/Pstream/$libName/using:$FOAM_MPI"...I must modify the "whichmpi" variable in the file OpenFOAM-v3.0+/src/Pstream/Allwmake in order to compile Openfoam-v3.0+
initial v3.0+ variable :
whichmpi="$WM_PROJECT_DIR/platforms/$WM_OPTIONS/src/Pstream/$libName/using:$FOAM_MPI"
modified v3.0+ variable (identical to 2.4.0 variable):
whichmpi="$libName/Make/$WM_OPTIONS/using:$FOAM_MPI"
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/854Empty Confirmation Mail - OpenFOAM Mailing List2018-06-04T09:43:03ZKutalmış BerçinEmpty Confirmation Mail - OpenFOAM Mailing ListHi,
I subscribed the newsletter three days ago, and received an email from `no-reply@openfoam.com via cp04.hosting.zen.net.uk`. The title reads `Confirm to join the OpenFOAM mailing list!`; so, I expected to see a confirmation click, b...Hi,
I subscribed the newsletter three days ago, and received an email from `no-reply@openfoam.com via cp04.hosting.zen.net.uk`. The title reads `Confirm to join the OpenFOAM mailing list!`; so, I expected to see a confirmation click, but the email is empty. Also nothing was blocked. I use `gmail.com`.
Then, today I used another mail provider. Everything was fine.
Assuming nothing has changed from your side, might be some problem with `gmail`?
PS: I have just checked with another gmail account. Email passed SPF check, but the whole content was somehow blocked. Here, the original content to diagnose: https://www.writeurl.com/text/1qxtxc2kvowyu55qmsp8/ar6q2cavoapfn8wh610a
Considering gmail is the most common provider, it might be useful to consider it.https://develop.openfoam.com/Development/openfoam/-/issues/44BUG: Validation case in parallel2016-01-05T05:31:40ZPrashant SonakarBUG: Validation case in parallelNaturalConvection/2D-Laminar/2DLaminarBuoyantCavity when run in parallel (4CPU, scotch decomposition) produced incorrect results for Re 10e6 case.
@Mattijs NaturalConvection/2D-Laminar/2DLaminarBuoyantCavity when run in parallel (4CPU, scotch decomposition) produced incorrect results for Re 10e6 case.
@Mattijs Sergio FerrarisSergio Ferraris