OpenFOAM-plus issueshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues2022-07-12T16:36:07Zhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1306number of parcels stick to surface MPPICInterFoam2022-07-12T16:36:07Zrmnnumber of parcels stick to surface MPPICInterFoamI did a simulation with op1812 and MPPICInterFoam solver. I injected 550,000 parcels but more than 999M parcels stick to one of the boundaries.
this is part of the log file:
```
Courant Number mean: 0.111537 max: 0.968023
Interface Cour...I did a simulation with op1812 and MPPICInterFoam solver. I injected 550,000 parcels but more than 999M parcels stick to one of the boundaries.
this is part of the log file:
```
Courant Number mean: 0.111537 max: 0.968023
Interface Courant Number mean: 0 max: 0
deltaT = 0.00666667
Time = 314.193
Evolving kinematicCloud
Solving 3-D cloud kinematicCloud
GAMG: Solving for kinematicCloud:alpha, Initial residual = 0.0014182, Final residual = 0.00109688, No Iterations 1000
Cloud: kinematicCloud
Current number of parcels = 287167
Current mass in system = 1.57878e-10
Linear momentum = (2.97358e-15 -1.83809e-15 1.12724e-14)
|Linear momentum| = 1.1802e-14
Linear kinetic energy = 6.06593e-16
Injector model1:
- parcels added = 549986
- mass introduced = 3.02371e-10
Parcel fate: system (number, mass)
- escape = 262819, 1.44492e-10
Parcel fate: patch WALL_IN (number, mass)
- escape = 0, 0
- stick = 0, 0
Parcel fate: patch WALL_OUT (number, mass)
- escape = 0, 0
- stick = 0, 0
Parcel fate: patch LUMEN_WALL (number, mass)
- escape = 0, 0
- stick = 944675672, 5.19376e-07
Parcel fate: patch OUTLET (number, mass)
- escape = 262819, 1.44483e-10
- stick = 0, 0
Parcel fate: patch INLET (number, mass)
- escape = 0, 0
- stick = 0, 0
Min cell volume fraction = 0
Max cell volume fraction = 2.13323e-05
Min dense number of parcels = 5.5605
Continous phase-1 volume fraction = 1 Min(alphac) = 0.999979 Max(alphac) = 1
PIMPLE: iteration 1
smoothSolver: Solving for alpha.water, Initial residual = 0.013389, Final residual = 0.0114096, No Iterations 100
Phase-1 volume fraction = 1 Min(alpha.water) = 1 Max(alpha.water) = 1
MULES: Correcting alpha.water
MULES: Correcting alpha.water
Phase-1 volume fraction = 1 Min(alpha.water) = 1 Max(alpha.water) = 1
smoothSolver: Solving for alpha.water, Initial residual = 0.0115916, Final residual = 0.0115598, No Iterations 100
Phase-1 volume fraction = 1 Min(alpha.water) = 1 Max(alpha.water) = 1
MULES: Correcting alpha.water
MULES: Correcting alpha.water
Phase-1 volume fraction = 1 Min(alpha.water) = 1 Max(alpha.water) = 1
DICPCG: Solving for p_rgh, Initial residual = 2.09388e-06, Final residual = 9.41566e-08, No Iterations 4
time step continuity errors : sum local = 5.14021e-11, global = -8.3902e-12, cumulative = -6.26016e-09
DICPCG: Solving for p_rgh, Initial residual = 3.24005e-06, Final residual = 1.60079e-07, No Iterations 7
time step continuity errors : sum local = 8.73903e-11, global = -1.33005e-11, cumulative = -6.27346e-09
DICPCG: Solving for p_rgh, Initial residual = 1.38674e-06, Final residual = 9.51116e-09, No Iterations 442
time step continuity errors : sum local = 5.19234e-12, global = 3.77542e-15, cumulative = -6.27346e-09
ExecutionTime = 40261.9 s ClockTime = 40514 s
Courant Number mean: 0.111537 max: 0.968022
Interface Courant Number mean: 0 max: 0
deltaT = 0.00666667
Time = 314.2
```
I wanted to know if this bug solved in dev version or not.
Thanks in advance.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/289BUG: invalid type while accessing fields2020-01-07T01:32:11ZPrashant SonakarBUG: invalid type while accessing fieldsAttached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FO...Attached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FOAM FATAL IO ERROR:
unexpected class name volScalarField expected volVectorField
while reading object p
file: /hosts/pnq073/home/sonakar/share/pitzDaily-develop/5/p at line 15.
From function Foam::Istream& Foam::regIOobject::readStream(const Foam::word&)
in file db/regIOobject/regIOobjectRead.C at line 295.
End
```Version v1612Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1309foamExec file is missing2019-12-11T16:55:44ZAlifoamExec file is missingHi,
I have noticed that foamExec is not present in bin directory. Then I was tracking down the changes of that file and found that it was removed. I usually use qtcreator to compile my own solvers/utilities to keep my development update...Hi,
I have noticed that foamExec is not present in bin directory. Then I was tracking down the changes of that file and found that it was removed. I usually use qtcreator to compile my own solvers/utilities to keep my development updated and I need foamExec file for the compilation process. I am not sure, any other file can be used for that purpose or not.
solution: Just need to reinstate the file. I just copied foamExec file from the previous version and working with it.
Regards,
Ali
MUN, CanadaMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/938illegal instruction constexpr v1712 v18062019-12-11T16:42:55ZCole Muellerillegal instruction constexpr v1712 v1806Trying to compile a new solver on windows 10 bash with ubuntu. Compiler returns an error saying illegal instruction constexpr. This has occurred on versions 1712 and 1806 in the header file floatScalar.H. I believe it has been a repeated...Trying to compile a new solver on windows 10 bash with ubuntu. Compiler returns an error saying illegal instruction constexpr. This has occurred on versions 1712 and 1806 in the header file floatScalar.H. I believe it has been a repeated issue from what I have seen on the forums so others will probably be able to provide more information. I don't know if this is a version issue because I updated all my compilers. I only come because the only solution I have seen found to this anywhere is revert to OF5. I have seen this exact issue reported on v1706 as well.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1007source bashrc in WSL causes bash: eval: line 38: syntax error near unexpected...2019-12-11T12:50:50ZFoadsource bashrc in WSL causes bash: eval: line 38: syntax error near unexpected token `('I tried to load the bashrc in WSL but I get the error:
> bash: eval: line 38: syntax error near unexpected token `('
similar problem [here](https://stackoverflow.com/questions/51345463/syntax-error-near-unexpected-token-when-sourcing-b...I tried to load the bashrc in WSL but I get the error:
> bash: eval: line 38: syntax error near unexpected token `('
similar problem [here](https://stackoverflow.com/questions/51345463/syntax-error-near-unexpected-token-when-sourcing-bashrc-to-setup-openfoam-e).Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1511ensightReadFile ignores string limits2019-12-02T12:36:35ZMark OLESENensightReadFile ignores string limitsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1456sampledSet 'uniform' does not produce same output in parallel2019-12-02T10:36:43ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampledSet 'uniform' does not produce same output in parallel<!--
*** 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 ...<!--
*** 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 -->
different number of samples when run in parallel.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Take pitzDaily tutorial. Use decomposeParDict with
```
//- The total number of domains (mandatory)
numberOfSubdomains 2;
////- The decomposition method (mandatory)
method random;
```
There will be 10 tracks when running in parallel but only 1 when running in parallel.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : develop (but probably also v1906)
- Operating system : openSUSE
- 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
-->https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1514solid body motion solver does not work with rigid body solver2019-12-02T09:43:57ZAlisolid body motion solver does not work with rigid body solverHi,
I am trying to use solid body motion as a mesh motion solver for rigid body motion. Although it lists the solid body motion as a valid motion solver, it fails to cast solver type and crash at the beginning. I have attached dynamicMe...Hi,
I am trying to use solid body motion as a mesh motion solver for rigid body motion. Although it lists the solid body motion as a valid motion solver, it fails to cast solver type and crash at the beginning. I have attached dynamicMeshDict file which can be placed in floatingBody overset tutorial to reproduce the error. The error line
--> FOAM FATAL ERROR:
Attempt to cast type solidBody to type displacementMotionSolver
Regards,
Ali
[6DoF.dat](/uploads/b4482b95045d89f392cbb664abc39412/6DoF.dat)
[dynamicMeshDict](/uploads/090b4e4130601b0d00883af3c85c20dc/dynamicMeshDict)https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1512Porting OpenFOAM to Windows2019-12-02T06:26:05Zs1291Porting OpenFOAM to WindowsHello,
Yesterday I have opened an [issue about OpenFOAM filenames in Windows](https://github.com/blueCFD/Core/issues/136) in BlueCFD project. Bruno, told me to open an issue here as well. This might be a potential solution to the probl...Hello,
Yesterday I have opened an [issue about OpenFOAM filenames in Windows](https://github.com/blueCFD/Core/issues/136) in BlueCFD project. Bruno, told me to open an issue here as well. This might be a potential solution to the problem of file naming in Windows (case insensitive).
In summary:
* Windows 10 now offers an optional case-sensitive file system, just like Linux and other UNIX-like operating systems. But this could be enabled on per-directory basis.
* Newer C++ compilers that support C++17, have `__has_include` feature for conditional including.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1387Iso surface truncated by new "topo" method2019-11-28T12:07:44ZRiccardo RossiIso surface truncated by new "topo" methodDuring the same run in an external aerodynamics application, I have tried to use the new isoSurfaceTopo method to extract and visualize turbulent structures via Lambda2, which resulted in a troncated iso-surface near the object, as shown...During the same run in an external aerodynamics application, I have tried to use the new isoSurfaceTopo method to extract and visualize turbulent structures via Lambda2, which resulted in a troncated iso-surface near the object, as shown in the picture attached (orange is Lambda2 via standard isoSurface and blue Lambda2 via isoSurfaceTopo).
![isoSurfaceTopoComparison](/uploads/23a8cffff6f8c5c90b629363ef798f29/isoSurfaceTopoComparison.png)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1506wrong sampling in arraySet.C line 722019-11-28T11:53:39ZPer Jørgensenwrong sampling in arraySet.C line 72please change
`point pt(i*dx*i , j*dy, k*dz);`
to
`point pt(i*dx , j*dy, k*dz);`
- i am not allowed...please change
`point pt(i*dx*i , j*dy, k*dz);`
to
`point pt(i*dx , j*dy, k*dz);`
- i am not allowed...Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/84timeVaryingMappedFixedValue uses linear extrapolation if outside triangulation2019-11-27T16:07:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtimeVaryingMappedFixedValue uses linear extrapolation if outside triangulationtimevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest...timevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest triangle. This is generally not ideal and especially very high aspect ratio triangles it gives problems (e.g. interpolation weights (23937.3 -48293 24356.7)
I think we should use zero-gradient outside triangles.
https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1472dynamicCode should use polling instead of re-checking only once2019-11-27T14:16:35ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdynamicCode should use polling instead of re-checking only once### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' secon...### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' seconds and rechecks. If this fails the code will fail. Nicer if the check gets done multiple times before failing.
Alternatively send over the library (is this possible? is it cross-node compatible?)https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1513applyBoundaryLayer : fails when cell is disconnected2019-11-27T13:00:05ZPrashant SonakarapplyBoundaryLayer : fails when cell is disconnected<!--
*** 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 ...<!--
*** 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
For disconnected cells wallDistance can have -1e15 (i.e. -GREAT) value, which can cause issue with ::pow
cross ref : EP#1158
<!-- Summarize the bug encountered concisely -->
### What is the current *bug* behaviour?
Fails with error (discriminator 1)
<!-- What actually happens -->
### Possible fixes
Warn user for non-visited cells. And protection in ::pow function?
<!--
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
-->
@Mattijshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1465turbulentDFSEMInlet for LES imulation for naca0012 aerofoil2019-11-26T10:49:06Zzein elserfyturbulentDFSEMInlet for LES imulation for naca0012 aerofoil<!--
*** 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 ...<!--
*** 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
I am trying to use turbulentDFSEMInlet at the inlet for simulation flow over aerofoil (The domain is attached below
domain size ( 5c upstream, 10 c downstream and spanwise 0.1 c ) c is the chord length (c=0.3048 m) and in the log file at the first time step only 5 eddies are generated at the inlet as shown below
`starting time loop
Courant Number mean: 0.000449944 max: 0.0468918
deltaT = 1.2e-07
Time = 1.2e-07
PIMPLE: iteration 1
**Turbulent DFSEM patch: inlet seeded 5 eddies with total volume 0.0519412**
smoothSolver: Solving for Ux, Initial residual = 3.70186e-06, Final residual = 5.58285e-09, No Iterations 1
smoothSolver: Solving for Uy, Initial residual = 2.02752e-06, Final residual = 7.27509e-08, No Iterations 1
smoothSolver: Solving for Uz, Initial residual = 0.000726498, Final residual = 8.2538e-08, No Iterations 1
GAMG: Solving for p, Initial residual = 0.999923, Final residual = 1.86291, No Iterations 1000
GAMG: Solving for p, Initial residual = 0.0407024, Final residual = 0.0142608, No Iterations 1000
time step continuity errors : sum local = 9.09561e-07, global = -1.32729e-08, cumulative = -1.32729e-08
GAMG: Solving for p, Initial residual = 0.0149751, Final residual = 0.00549751, No Iterations 1000
GAMG: Solving for p, Initial residual = 0.0055067, Final residual = 0.00168609, No Iterations 1000
time step continuity errors : sum local = 1.49201e-07, global = -4.97451e-09, cumulative = -1.82474e-08`
### Steps to reproduce
**boundary conditions**
`/*--------------------------------*- C++ -*----------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: v1906 |
| \\ / A nd | Web: www.OpenFOAM.com |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
FoamFile
{
version 2.0;
format ascii;
class volVectorField;
object U;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
dimensions [ 0 1 -1 0 0 0 0 ];
internalField uniform ( 71.3 0 0 );
boundaryField
{
aerofoil
{
type fixedValue;
value uniform ( 0 0 0 );
}
top
{
type symmetryPlane;
}
bottom
{
type symmetryPlane;
}
front
{
type cyclic;
}
back
{
type cyclic;
}
inlet
{
type turbulentDFSEMInlet;
delta 2;
nCellPerEddy 3;
mapMethod nearestCell;
R uniform (0.5 0 0 0.5 0 0.5);
U uniform (71.3 0 0);
L uniform 0.055;
value $internalField;
}
outlet
{
type freestream;
freestreamValue uniform (71.3 0 0);
value uniform (71.3 0 0);
}
}
// ************************************************************************* //`
`
FoamFile
{
version 2.0;
format ascii;
class dictionary;
location "constant";
object turbulenceProperties;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
simulationType LES;
LES
{
LESModel kEqn;
turbulence on;
printCoeffs on;
delta vanDriest;
vanDriestCoeffs
{
delta cubeRootVol;
cubeRootVolCoeffs
{
deltaCoeff 1;
}
Aplus 26;
Cdelta 0.158;
}
}
// ************************************************************************* //`
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
### What is the current *bug* behaviour?
only 5 eddies are generated at the inlet and inlet velocity higher than average specified velocity as shown in the attached picture (velocity inlet=113 although the Umean=71.3 m/s)
![Capture](/uploads/15f090f2c4897ce376acd3550064832d/Capture.JPG)![Capture1](/uploads/98ff8a5078c628de6df3a034dc79a67c/Capture1.JPG)
### What is the expected *correct* behavior?
<expected higher numbers of eddies are generated at the inlet with umean=71.3 m/s
### Relevant logs and/or images
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version :1906
- Operating system :ubuntu 15.04
- 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
-->https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1510support specified time for trasformPoints2019-11-25T18:34:03ZPrashant Sonakarsupport specified time for trasformPoints### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constant### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/562simulation stop at reaching a preset wall time2019-11-25T07:22:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsimulation stop at reaching a preset wall timeFeature to stop the simulation at a prescribed wall time (and write the results?). This is for running under batch queueing systems to avoid them killing the job. (or can the queueing system 'warn' us when it wants us to stop (and give s...Feature to stop the simulation at a prescribed wall time (and write the results?). This is for running under batch queueing systems to avoid them killing the job. (or can the queueing system 'warn' us when it wants us to stop (and give some time for writing)?)https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/545Problem with BC for upwind discretization causing oscillating/negative soluti...2019-11-22T17:29:16ZGedProblem with BC for upwind discretization causing oscillating/negative solution (tested in 1D scalarTransportFoam)As described here
https://www.cfd-online.com/Forums/openfoam-bugs/188749-negative-values-scalartransportfoam-upwind-discretization.html
the usage of upwind discretization does not prevent the appearance of oscillations in the scalar fiel...As described here
https://www.cfd-online.com/Forums/openfoam-bugs/188749-negative-values-scalartransportfoam-upwind-discretization.html
the usage of upwind discretization does not prevent the appearance of oscillations in the scalar field with scalarTransportFoam in the standard 1D convection-diffusion test case (i.e. T(0)=0 and T(L)=1 with advection dominated flow), where the region with the high gradient is located directly at the x=L boundary.
If the gradient is located in the volume (by adding a volume source term for T vie the fvOptions and setting the BC at x=L to zeroGradient), the upwind discretization behaves as expected, giving a smooth (overly-diffusive) solution over the entire volume. This points to a problem with the boundary conditions.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1497Error decomposing with redistributePar and codedFixedValue BC2019-11-21T13:48:52ZCarlos Peña-MonferrerError decomposing with redistributePar and codedFixedValue BC<!--
*** 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 ...<!--
*** 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
Decomposing a case with `redistributePar` fails when `codedFixedValue` boundary condition is used.
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
A minimal example with `pitzDaily` has been attached. The error appears when executing the following commands:
```
blockMesh
mpirun -np 16 redistributePar -parallel -decompose
```
<!-- How one can reproduce the issue - this is very important -->
### Example case
`pitzDaily` tutorial. `0/U` file modified for reproducing the error.
[pitzDailyTest.zip](/uploads/a516c651c6e06aef2e2a8027c9156628/pitzDailyTest.zip)
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
### What is the current *bug* behaviour?
Trying to decompose with `redistributePar` any case that includes `codedFixedValue` fails.
Decomposition works with `decomposePar`, or `fixedValue` and `redistributePar` but fails including a basic `codedFixedValue` BC.
<!-- What actually happens -->
### Relevant logs and/or images
```
[10] --> FOAM FATAL IO ERROR:
[10] Attempt to put back onto bad stream
[10]
[10] file: IOstream at line 0
[11]
[11] file: IOstream.
[9]
[9] From function [5]
FOAM parallel run exiting
```
<!--
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v1906
- Operating system : centos
- Compiler : gcc
<!--
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
-->https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1508isoSurfaceTopo not passing through ACMI2019-11-21T09:47:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comisoSurfaceTopo not passing through ACMIRun oscillatingInletACMI2D tutorial with
```
isoSurfaceTopo
{
type surfaces;
libs ("libsampling.so");
enabled true;
writeControl timeStep;
writeInterval 1;
interpolationScheme cellPoint;
surfaceFo...Run oscillatingInletACMI2D tutorial with
```
isoSurfaceTopo
{
type surfaces;
libs ("libsampling.so");
enabled true;
writeControl timeStep;
writeInterval 1;
interpolationScheme cellPoint;
surfaceFormat vtk;
// Fields to be sampled
fields
(
p
U
);
surfaces
(
isoSurface1
{
type isoSurfaceTopo;
patches ( ".*");
isoField p;
isoValue 0.1;
interpolate true;
triangulate false;
regularise cell; //diagcell;
}
);
}
```
and the isosurface does not pass through the acmi. This is due to the duplicate faces (ACMI+wall) on either side of the ACMI.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com