Development issueshttps://develop.openfoam.com/groups/Development/-/issues2023-12-04T15:34:28Zhttps://develop.openfoam.com/Development/openfoam/-/issues/3039facGrad not compatible with cache of gradient2023-12-04T15:34:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfacGrad not compatible with cache of gradient### Summary
fac::grad manipulates result from fa::gradScheme<Type>. If this is a cached result it tries to modify the cached value.
### Steps to reproduce
tutorial `finiteArea/liquidFilmFoam/cylinder` with
```
cache
{
grad(h);
...### Summary
fac::grad manipulates result from fa::gradScheme<Type>. If this is a cached result it tries to modify the cached value.
### Steps to reproduce
tutorial `finiteArea/liquidFilmFoam/cylinder` with
```
cache
{
grad(h);
grad(Us);
}
```
### Example case
See above
### What is the current *bug* behaviour?
Attempted non-const access to const-ref:
```
--> FOAM FATAL ERROR: (openfoam-2309)
Attempted non-const reference to const object: tmp<N4Foam14GeometricFieldINS_6VectorIdEENS_12faPatchFieldENS_8areaMeshEEE>
```
### What is the expected *correct* behavior?
<!-- What you should see instead -->
### Relevant logs and/or images
See above
### Environment information
- OpenFOAM version : v2309
### Possible fixes
Move caching up to this level?Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/3038SRFModel tmp early release2023-11-30T17:56:13ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comSRFModel tmp early release<!--
*** 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 -->
SRFModel illegal tmp use
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Run SRFPimpleFoam tutorial:
```
--> FOAM FATAL ERROR: (openfoam-2309)
tmp<N4Foam14GeometricFieldINS_6VectorIdEENS_12fvPatchFieldENS_7volMeshEEE> deallocated
```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2306|v2212|v2206|v2112|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2308
### 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
-->
Introduced in !628Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/3036epsilonWallFunction: Expression of espilon in log layer2023-11-27T17:35:31Zs1291epsilonWallFunction: Expression of espilon in log layerIn this documentation page about [`epsilonWallFunction`](https://www.openfoam.com/documentation/guides/latest/doc/guide-bcs-wall-turbulence-epsilonWallFunction.html), the expression of $\epsilon_\text{log}$ is given by:
$$
\epsilon_\tex...In this documentation page about [`epsilonWallFunction`](https://www.openfoam.com/documentation/guides/latest/doc/guide-bcs-wall-turbulence-epsilonWallFunction.html), the expression of $\epsilon_\text{log}$ is given by:
$$
\epsilon_\text{log} = wC_\mu\frac{k^{3/2}}{\nu_{t,w}y} \tag{1}
$$
However, in the [source code](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/TurbulenceModels/turbulenceModels/derivedFvPatchFields/wallFunctions/epsilonWallFunctions/epsilonWallFunction/epsilonWallFunctionFvPatchScalarField.C#L225), the following expression is used:
$$
\epsilon_\text{log} = wC_{\mu}^{3/4}\frac{k^{3/2}}{\kappa y} \tag{2}
$$
Unless the expressions $\frac{C_\mu}{\nu_{t,w}}$ and $\frac{C_{\mu}^{3/4}}{\kappa}$ are equivalent, the expression (1) should be corrected in the documentation.
Thank youhttps://develop.openfoam.com/Development/openfoam/-/issues/2788openfoam conda2023-11-26T17:23:29ZHenning Scheufleropenfoam condaA possibility to install OpenFOAM without admin rights is conda:
https://github.com/HenningScheufler/conda-openfoam
The installation process would be quite straightforward. Download and install the miniconda then run following commands...A possibility to install OpenFOAM without admin rights is conda:
https://github.com/HenningScheufler/conda-openfoam
The installation process would be quite straightforward. Download and install the miniconda then run following commands:
```bash
conda create -n openfoam # create new env named openfoam
conda activate openfoam # activate the enviroment
conda install openfoam -c conda-forge # download and install openfoam from conda forge
```
This could simplify the installation on workstations. For HPC spack is probably the better optionhttps://develop.openfoam.com/Development/openfoam/-/issues/1977Contribution: Dynamic load balancing for combustion simulations2023-11-24T16:26:56ZBulut TekgulContribution: Dynamic load balancing for combustion simulationsDear all,
I am writing behalf of my research group in Aalto University, Finland. Recently we have developed a custom chemistry model called DLBFoam that mitigates the well-known computational load imbalance issue in multi-processor reac...Dear all,
I am writing behalf of my research group in Aalto University, Finland. Recently we have developed a custom chemistry model called DLBFoam that mitigates the well-known computational load imbalance issue in multi-processor reactive CFD simulations using finite-rate chemistry and provides speed-up by 10 fold. Our model consists of two main features:
* A dynamic load balancer that uses MPI routines to balance the load between the processors during runtime
* A zonal reference mapping model based on Bilger's mixture fraction to map the chemistry solution of the cells from a reference solution instead of explicitly solving them, when applicable.
![crab pet](https://i.imgur.com/yYVBgHV.gif)
Our code is very well written and implemented with following OpenFOAM's code structure and guidelines and can be found in our public repository:
[GitHub - DLBFoam](https://github.com/blttkgl/DLBFoam)
You can find the branch called v1.0_OF2006 to see the version compatible with OpenFOAM ESI.
In addition, the preprint describing the code in great detail and providing benchmarking results are available at:
[ArXiv - DLBFoam](https://arxiv.org/abs/2011.07978)
There are still some things that need to be ironed out for a fully compatible contribution.
Minor:
* The Bilger's mixture fraction that we implement ourselves can be easily changed with the Bilger's mixture fraction that is implemented to OpenFOAM a while ago: [Issue Link](https://develop.openfoam.com/Development/openfoam/-/issues/1915)
Major:
* The chemistry model **at the moment** is derived from StandardChemistryModel and it does not extend to TDACChemistryModel. However, this is a low hanging fruit and can be easily implemented in a future release by us.
Finally, we will be rolling out some major changes to DLBFoam in the near future, such as replacing the finite-difference Jacobian of the chemistry ODE system with an analytical solution and using optimized matrix routines for the ODE solver. Combined with these features, we report speedup in the order of 200x in large 3D cases compared to StandardChemistryModel. Unlike DLBFoam at its current state these features are dependent on some open-source third party libraries but we would be glad to share them as well as contributions.
Please let me know if you are interested with this contribution and if yes what else would you require from us to move on with the contribution process. I will be following this thread but also feel free to reach at to me from bulut.tekgul@aalto.fi
Best,
Buluthttps://develop.openfoam.com/Development/openfoam/-/issues/1601Feature request: sedFOAM submodule2023-11-24T16:26:48ZKutalmış BerçinFeature request: sedFOAM submodule### Functionality to add/problem to solve
http://servforge.legi.grenoble-inp.fr/pub/soft-sedfoam/
https://github.com/sedfoam/sedfoam
Following the short discussion in their repo: https://github.com/SedFoam/sedfoam/issues/15
the mainta...### Functionality to add/problem to solve
http://servforge.legi.grenoble-inp.fr/pub/soft-sedfoam/
https://github.com/sedfoam/sedfoam
Following the short discussion in their repo: https://github.com/SedFoam/sedfoam/issues/15
the maintainer of sedFOAM showed keen interest on OpenFOAM's submodule functionality.
sedFOAM is represented as a code suite for two-phase flow sediment flow applications.
### Target audience
Wave/free surface involved applications, e.g. masts erected in sea bed, tidal turbines, or in general, underwater structures close to sea bed (might misunderstand).
### Proposal
If the maintenance cost of adding and shipping a new submodule is very low for OpenFOAM, sedFOAM submodule would be a win-win.
### What does success look like, and how can we measure that?
The suite is based on a set of publications, and has its own user group (it seems). Also, reasonably well maintained by a group of people, compatible with recent OF versions.
### Funding
NA
@andy @mark @Mattijs @Sergio @Prashant @RogerKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2978BUG: runTimeModifiable crashes with collated in rhoPimpleFoam2023-11-23T15:51:12ZAlberto ceschinBUG: runTimeModifiable crashes with collated in rhoPimpleFoam### Summary
It is not possible to modify i.e. `endTime` during run time in tutorial `compressible/rhoPimpleFoam/RAS/aerofoilNACA0012` in parallel with `-fileHandler collated` and `runTimeModifiable true`. On the contrary, other solvers ...### Summary
It is not possible to modify i.e. `endTime` during run time in tutorial `compressible/rhoPimpleFoam/RAS/aerofoilNACA0012` in parallel with `-fileHandler collated` and `runTimeModifiable true`. On the contrary, other solvers behaeve as expected.
### Steps to reproduce
copy tutorial
`OpenFOAM-v2306/tutorials/compressible/rhoPimpleFoam/RAS/aerofoilNACA0012`
into run folder;
`foamGetDict decomposeParDict`;
Reduce number of cores to 4 and eliminate what is after scotch from the dictionary;
Increase `endTime` to `100`;
`./Allrun` but in parallel with
`runApplication decomposePar -fileHandler collated`;
`runParallel rhoPimpleFoam -fileHandler collated`;
at the end.
Change `endTime` to `101` during run time;
### What is the current *bug* behaviour?
```ExecutionTime = 13.52 s ClockTime = 13 s
From virtual bool Foam::regIOobject::readIfModified()
in file db/regIOobject/regIOobjectRead.C at line 271
Re-reading object controlDict from file "/home/username/OpenFOAM/username-v2306/run/FOAM_RUN/system/controlDict"
[0]
[0]
[0] --> FOAM FATAL IO ERROR: (openfoam-2306)
[0] Cannot find file "/home/username/OpenFOAM/username-v2306/run/FOAM_RUN/processor0/system/controlDict" fileHandler : comm:0 ioRanks:4(0 1 2 3)
[0]
[0] From static Foam::autoPtr<Foam::ISstream> Foam::fileOperations::masterUncollatedFileOperation::read(Foam::IOobject&, Foam::label, bool, const fileNameList&, const boolUList&)
[0] in file global/fileOperations/masterUncollatedFileOperation/masterUncollatedFileOperation.C at line 526.
[0]
FOAM exiting
[0]
--------------------------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:
Process name: [[8529,1],0]
Exit code: 1
-------------------------------------------------------------------------
```
### Environment information
OpenFOAM version : v2306
Operating system : ubuntu 22https://develop.openfoam.com/Development/openfoam/-/issues/3032redistributePar slow with preservePatches cosntraint2023-11-23T07:14:20ZTimofey MukharedistributePar slow with preservePatches cosntraintFollow-up to #2924, but not necessarily related in terms of what causes the issue.
To reliably decompose cyclic boundaries with `redistributePar` we currently need to use the `preservePatches` constraint for the cyclic boundaries. Unfor...Follow-up to #2924, but not necessarily related in terms of what causes the issue.
To reliably decompose cyclic boundaries with `redistributePar` we currently need to use the `preservePatches` constraint for the cyclic boundaries. Unfortunately, this seems to cause a strong dip in performance of the utility. According to @Mattijs this should not really happen. I have first observed this on my own case, but now got some numbers using the `periodicHill` tutorial.
I use the `steadyState` case in the tutorial, bump the number of processors in `decomposeParDict` to 32, and accordingly switch to 4 partitions along y. Additionally, we add
```
constraints
{
patches
{
//- Keep owner and neighbour on same processor for faces in patches
// (only makes sense for cyclic patches and cyclicAMI)
type preservePatches;
patches (inlet outlet);
}
}
```
which we can comment and uncomment to compare.
Furthermore, it is better to make the case a bit larger, so in `blockMeshDict` we set the size of the `hex` to `(200 160 400)`, and then run `blockMesh`.
Now, we decompose the case with
`time mpirun -n 32 redistributePar -decompose -latestTime -parallel -fileHandler collated`
On my machine, I get a 3x slowdown when preserving the patches.https://develop.openfoam.com/Development/openfoam/-/issues/2924resdistributePar -decompose fails in postChannel tutorial2023-11-22T07:22:27ZTimofey MukharesdistributePar -decompose fails in postChannel tutorial<!--
*** 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
Running
`mpirun 36 redistributePar -decompose -parallel`
in `planeChannel/results/DFSEM` crashes with
`[20] Cannot find point in pts1 matching point 0 coord:(57.65 0.88207685 3.1415927) in pts0 when using tolerance 6.2398167e-06`
and a following cascade of errors.
### Steps to reproduce
Go to the planeChannel tutorial, and run ./Allrun to generate the cases. Then execute `redistributePar` as above.
### A comment
I would like to stress that getting this utility to work properly, also in conjunction with the collated file format, is absolutely critical for LES/DNS runs. Serial `decomposePar` is just no longer an option, once the number of processors is in the order of thousands.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : master @ spack
- Operating system : Linux
- Hardware info : LUMI C node/ AMD EPYC 7742 64-Core Processor
- Compiler : gcc (SUSE Linux) 7.5.0Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/3009Nastran parser does not handle newer ANSA conventions2023-11-21T22:57:31ZMark OLESENNastran parser does not handle newer ANSA conventionsAlthough the Nastran format does not support names for shells etc, both Hypermesh and ANSA have their own conventions for using/misusing comments to convey that extra information. The nastran parser needs an update to handle the newer AN...Although the Nastran format does not support names for shells etc, both Hypermesh and ANSA have their own conventions for using/misusing comments to convey that extra information. The nastran parser needs an update to handle the newer ANSA conventions that are now circulating. The benefit is that this will allow more direct use of Nastran surface files elsewhere (eg, snappy).
cross-ref EP2299
@martin.lichtmes
Some notes (courtesy Martin Lichtmes)
---
### Type 1 - ANSA 19.0.1:
Region names contained in comment line immediately above respective PSHELL line.
- Header info: <br>
ANSA version
Output format specification [MSC|NX|AUTODESK] (no effect on file content detected)
- Footer info: <br>
$ANSA_NAME_COMMENTS etc. but not relevant for region naming
PSHELL info: Region names in commentary line immediately above (single string)
### Type 2 - ANSA 23.1.0:
Region names contained in footer section as part of $ANSA_NAME_COMMENT (fourth semicolon-separated entry).
- Header info: <br>
ANSA version
Output format specification [MSC|NX|AUTODESK] (no effect on file content detected)
- Footer info: <br>
$ANSA_NAME_COMMENT relevant for region naming
PSHELL info: No relevant/commentary information for region naming
### Type 3 - Possibly ANSA/unknown:
Region names contained in comment line immediately above respective PSHELL line.
- Header info: None
- Footer info: None
PSHELL info: Region names in commentary line immediately above (single string)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/3031BUG: multiple mapFields2023-11-21T14:27:42ZKutalmış BerçinBUG: multiple mapFields### Summary
The problem is that, apart from the first 'mapFields' function object, the following 'mapFields' function objects don't appear to be registering the fields they're working on to the correct region. For instance, in the probl...### Summary
The problem is that, apart from the first 'mapFields' function object, the following 'mapFields' function objects don't appear to be registering the fields they're working on to the correct region. For instance, in the problematic case below, the 'mapFields2' function object maps the 'UMean' from 'region0' to 'coarseMesh'. However, the object registry of 'coarseMesh' lacks any 'UMean'.
### Steps to reproduce
[2274-multiple-mapFields-21Nov23-GitLab.zip](/uploads/656e6c1e94ae2143f2373bad13ea4927/2274-multiple-mapFields-21Nov23-GitLab.zip)
### Environment information
api = 2308
HEAD = 0ae6141397
compiler = clang version 15.0.7
mpi = mpirun (Open MPI) 1.10.7.0.5e373bf1fd
OS = openSUSE Leap 15.5
opts = linux64ClangDPInt32Opt
@Mattijshttps://develop.openfoam.com/Development/openfoam/-/issues/2925Tensor operations: taking the inner product of three tensors produces a diffe...2023-11-17T19:24:36ZRyley McConkeyTensor operations: taking the inner product of three tensors produces a different result depending on if an intermediate variable is used<!--
*** 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
The following operations do not produce the same result for C :
1. C = A & A & A;
2. B = A & A; then C = B & A;
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Here is an example set of operations. Tensors B2a and B2b should be equal (since they are both S & S & S), but the results are different.
```
S = symm(fvc::grad(U));
B1 = S & S;
B2a = S & S & S;
B2b = B1 & S;
```
### 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
-->
I have attached an example case and example application that writes the above two results.
### What is the current *bug* behaviour?
A different result is produced for the two operations.
<!-- What actually happens -->
### What is the expected *correct* behavior?
The two operations should produce the same result. I believe the second result (after using an intermediate variable) is correct mathematically. I am not sure yet what operation is being performed in the first case (S & S & S).
<!-- What you should see instead -->
### 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.
-->
![Screenshot_from_2023-06-29_14-10-26](/uploads/cd1596da5d86af14d126bc93c02b109d/Screenshot_from_2023-06-29_14-10-26.png)
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2112
- 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
-->[case_0p5.zip](/uploads/bb01c9483630e4766047cdd604e4a897/case_0p5.zip)[writeFields_test.zip](/uploads/e1acfc378b8ff008c795511c01ca5bec/writeFields_test.zip)Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/3029Adding the repositories and trying to update apt in WSL with Ubuntu 18.04 LTS...2023-11-16T15:27:35ZMatti ViljamaaAdding the repositories and trying to update apt in WSL with Ubuntu 18.04 LTS reports 404 Not found on some URLs even though the URLs work in a browser.<!--
*** 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 -->
Adding the repositories and trying to update apt in WSL with Ubuntu 18.04 LTS reports 404 Not found on some URLs even though the URLs work in a browser.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
I am using WSL with Ubuntu 18.04 LTS and the guide at:
https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/windows
and in particular:
https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/debian
I am doing:
`curl https://dl.openfoam.com/add-debian-repo.sh | sudo bash`
and adding trusted=yes to:
deb [trusted=yes arch=amd64] https://dl.openfoam.com/repos/deb bionic main
in
/etc/apt/sources.list.d/openfoam.list
(This fixes another problem with the repositories. You can see the problem by removing trusted=yes.)
After this, shell reports 404 on some urls when doing the `sudo apt-get update` even though the URL (https://downloads.sourceforge.net/project/openfoam/repos/deb/dists/bionic/main/binary-amd64/Packages?ts=gAAAAABlU0ddE33NYF2BYJCrUgKdzm3tdc4pT5s50s0bO4jq_uOT3e-imqmuDbyW9FG41PrmLX9L7rvax9Dfyt7RR5uaZ2ydbg==&use_mirror=master&r=) itself works in a browser. Full output:
```
sudo apt-get update
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Ign:5 https://sourceforge.net/projects/openfoam/files/repos/deb bionic InRelease
Ign:6 https://sourceforge.net/projects/openfoam/files/repos/deb bionic Release
Ign:7 https://dl.openfoam.com/repos/deb bionic/main amd64 Packages
Ign:8 https://dl.openfoam.com/repos/deb bionic/main all Packages
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:7 https://dl.openfoam.com/repos/deb bionic/main amd64 Packages
Ign:8 https://dl.openfoam.com/repos/deb bionic/main all Packages
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:7 https://dl.openfoam.com/repos/deb bionic/main amd64 Packages
Ign:8 https://dl.openfoam.com/repos/deb bionic/main all Packages
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:9 https://dl.openfoam.com/repos/deb bionic/main Translation-en
Ign:10 https://dl.openfoam.com/repos/deb bionic/main all c-n-f Metadata
Ign:11 https://dl.openfoam.com/repos/deb bionic/main amd64 c-n-f Metadata
Ign:7 https://sourceforge.net/projects/openfoam/files/repos/deb bionic/main amd64 Packages
Ign:7 https://sourceforge.net/projects/openfoam/files/repos/deb bionic/main amd64 Packages
Ign:7 https://dl.openfoam.com/repos/deb bionic/main amd64 Packages
Ign:7 https://dl.openfoam.com/repos/deb bionic/main amd64 Packages
Ign:8 https://sourceforge.net/projects/openfoam/files/repos/deb bionic/main all Packages
Ign:8 https://sourceforge.net/projects/openfoam/files/repos/deb bionic/main all Packages
Ign:8 https://dl.openfoam.com/repos/deb bionic/main all Packages
Ign:8 https://dl.openfoam.com/repos/deb bionic/main all Packages
Err:7 https://sourceforge.net/projects/openfoam/files/repos/deb bionic/main amd64 Packages
404 Not Found [IP: 82.71.205.33 443]
Reading package lists... Done
E: Failed to fetch https://downloads.sourceforge.net/project/openfoam/repos/deb/dists/bionic/main/binary-amd64/Packages?ts=gAAAAABlU0ddE33NYF2BYJCrUgKdzm3tdc4pT5s50s0bO4jq_uOT3e-imqmuDbyW9FG41PrmLX9L7rvax9Dfyt7RR5uaZ2ydbg==&use_mirror=master&r= 404 Not Found [IP: 82.71.205.33 443]
E: Failed to fetch https://downloads.sourceforge.net/project/openfoam/repos/deb/dists/bionic/main/binary-all/Packages?ts=gAAAAABlU0ddOvkkOuXCeg05riwpnOabnmAYq42Yl6AoBItkbuf95la7On9UFcH_JnZb9QeAH4IobNvAs2ekXvWON2UqNm0oVQ==&use_mirror=master&r= 404 Not Found [IP: 82.71.205.33 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
```
### 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?
<!-- What actually happens -->
### What is the expected *correct* behavior?
<!-- What you should see instead -->
No errors.
### 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 : v2306|v2212|v2206|v2112|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2306
- Operating system : WSL Ubuntu 18.04 LTS
- 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
-->
Based on some threads like:
https://unix.stackexchange.com/questions/148303/apt-get-install-gives-404-not-found-but-url-works
it could be a bug with apt.
Or it could be a problem with the installer script.https://develop.openfoam.com/Development/openfoam/-/issues/3028non-orthogonal faces to set nonOrthoFaces2023-11-16T15:22:11ZFarshad Ansarinon-orthogonal faces to set nonOrthoFacesHello,
When I import my data.unv with the ideasUnvToFoam command, everything is ok. But after meshCheck I get this error:
*Number of severely non-orthogonal (> 70 degrees) faces: 612.
Non-orthogonality check OK.
<<Writing 612 no...Hello,
When I import my data.unv with the ideasUnvToFoam command, everything is ok. But after meshCheck I get this error:
*Number of severely non-orthogonal (> 70 degrees) faces: 612.
Non-orthogonality check OK.
<<Writing 612 non-orthogonal faces to set nonOrthoFaces
Face pyramids OK.
Max skewness = 1.23757 OK.
Coupled point location match (average 0) OK.
Failed 1 mesh checks.
what should I do?
thankshttps://develop.openfoam.com/Development/openfoam/-/issues/3027Evaporation of two liquid phases using icoReactingMultiphaseInterFoam2023-11-16T15:20:51ZMark YEvaporation of two liquid phases using icoReactingMultiphaseInterFoam### Summary
The Solver I used is the icoReactingMultiphaseInterFoam V2306, the Ubuntu version is 20.04.
I try to simulate two different liquid droplets, i.e., liquid1 and liquid2, evaporating to the gas phase. If I set two liquid drop...### Summary
The Solver I used is the icoReactingMultiphaseInterFoam V2306, the Ubuntu version is 20.04.
I try to simulate two different liquid droplets, i.e., liquid1 and liquid2, evaporating to the gas phase. If I set two liquid droplets, the vapor of the liquid, i.e., vapor1, occurs in both two locations, see the picture(the same as vapor2). Physically, vapor1 should occur in location 1 and vapour2 should occur at location 2.
![figure](/uploads/1b20be65014dcb0ad7784a44b6f28dee/figure.png)
I found the code to calculate the massSpeciesTransfer in multiphaseInter::MassTransferPhaseSystem.C. No matter what species is transferred from the liquid phase (liquid1 or liquid2), the value of Su is the same.
The attached is the setting case.[debug.tar.gz](/uploads/83421f905cc567ec6fd5249dac37fee9/debug.tar.gz)https://develop.openfoam.com/Development/openfoam/-/issues/3026rigidBodyMotion linearAxialAngularSpring theta angle appears to be incorrectl...2023-11-16T15:20:33ZChristian RohrrigidBodyMotion linearAxialAngularSpring theta angle appears to be incorrectly signed - spring acts in wrong direction### Summary
Theta angle used in (at least) `linearAxialAngularSpring.C` in the rigidBodyMotion solver appears to be signed incorrectly.
### Steps to reproduce
Apply the linearAxialAngularSpring restraint to a body, and observe it be p...### Summary
Theta angle used in (at least) `linearAxialAngularSpring.C` in the rigidBodyMotion solver appears to be signed incorrectly.
### Steps to reproduce
Apply the linearAxialAngularSpring restraint to a body, and observe it be pulled in the wrong direction. Have tested with pimpleDyMFoam. This has occured on another case which I cannot share, so I have created a new one from one of the tutorials.
Modifying the code for this restraint to ouptut the current angular position shows that the "theta" variable is signed incorrectly. For example a clockwise rotation around the z axis of 45° will be reported as 45° instead of -45°.
### Example case
Attached a case modified from the overset airfoil simpleFoam tutorial. It has been made transient, switched to rigidBody, and a spring constraint has been applied. Increasing the stiffness of this spring exacerbates the movement of the airfoil rather than assisting.
[testCase_axialSpring.zip](/uploads/676fc081bc3e63b66c9376639aa163e3/testCase_axialSpring.zip)
### What is the current _bug_ behaviour?
Spring moment acts in wrong direction.
### What is the expected _correct_ behavior?
A positive rotation should create a negative torque.
### Relevant logs and/or images
In the example case, I have attached a spring at the bottom of the domain to the airfoil with an Rz joint. The spring pulls the airfoil down and to the right, and this is accelerated for higher spring stiffnesses. Some movement in that direction is expected for the aerodynamic load, but it should reduce with increasing stiffness rather than worsen.
The case should be run with a stiffness of 1 and then with a stiffness of 100 to observe the issue.
Alternatively, add an `Info <<` message reporting the theta angle of the airfoil body at line 143 of `linearAxialAngularSpring.C` : it is signed incorrectly for the observed rotations.
![image.png](/uploads/71c2ddc6030e147d4b073b8df15267aa/image.png){width="314" height="299"}
### Environment information
- OpenFOAM version : v2112
- Operating system : WSL - OpenSUSE Leap 15.4
- Hardware info : x86_64
- Compiler : gcc
### Possible fixes
Manual flip to theta's sign on line `112` of `linearAxialAngularSpring.C`. But I have not been able to get to the bottom of why this is incorrectly signed to begin with. Could this just be due to case configuration?https://develop.openfoam.com/Development/openfoam/-/issues/2998Lagrangian ConeInjection model fails to restart smoothly2023-11-14T18:53:27ZAndrew HeatherLagrangian ConeInjection model fails to restart smoothlyWhen restarting cases with the ConeInjection injector model parcels typically fail to be injected/incorrect counts recorded.
Cross ref: EP2280When restarting cases with the ConeInjection injector model parcels typically fail to be injected/incorrect counts recorded.
Cross ref: EP2280v2312Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/3018pTraits for complex looks incorrect2023-11-13T13:53:25ZMark OLESENpTraits for complex looks incorrectThe complex type is defined to have two components (ie, real, imag) but has cmptType as "complex" - doesn't really make sense, and has labelType as label anyhow.
It doesn't seem to be used anywhere but could be interesting with different...The complex type is defined to have two components (ie, real, imag) but has cmptType as "complex" - doesn't really make sense, and has labelType as label anyhow.
It doesn't seem to be used anywhere but could be interesting with different backends (eg ADIOS).
@andy @kutiv2406Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2989surfaceFieldValue: Not all patches in 'names' list are reported in Info stream2023-11-09T23:23:29ZMartin LichtmessurfaceFieldValue: Not all patches in 'names' list are reported in Info stream<!--
*** 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
When evaluating multiple patches in surfaceFieldValue FO using 'names' keyword, not all patch names seem to be reported back in Info stream, whereas the numerical value appears to be correct - only first patch name in list? - May cause confusion as to which patches contribute to the evaluation.
### Steps to reproduce
1. Set up surfaceFieldValue FO using list of patches (e.g. 'names (inlet, outlet)' in pitzDaily) and apply 'sum' operation
2. Run case and monitor info stream/solver output regarding surfaceFieldValue evaluation
### Example case
$FOAM_TUTORIALS/incompressible/pisoFoam/LES/pitzDaily
### What is the current *bug* behaviour?
Log snippet for three FOs (1. 'name inlet', sum(phi); 2. 'name outlet', sum(phi); 3. 'names (inlet outlet), sum(phi)):
```
surfaceFieldValue namesTest_inlet write:
sum(inlet) of phi = -0.000253241
surfaceFieldValue namesTest_outlet write:
sum(outlet) of phi = 0.000253241
surfaceFieldValue namesTest_inlet_outlet write:
sum(inlet) of phi = 2.09431e-11
```
### What is the expected *correct* behavior?
```
surfaceFieldValue namesTest_inlet_outlet write:
sum(inlet, outlet) of phi = 2.09431e-11
```
### 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
- OpenFOAM version : v2306
- Operating system : Ubuntu WSL/RedHat 8
### 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/-/issues/3007IOobject requires global path and object methods2023-11-09T23:20:57ZMark OLESENIOobject requires global path and object methodsAs part of integration efforts (@Serge and @gregorweiss) we need convenient access to both global path names (ie, the serial paths) as well as the processor paths. Need to propagate through some values from Time/TimePaths.As part of integration efforts (@Serge and @gregorweiss) we need convenient access to both global path names (ie, the serial paths) as well as the processor paths. Need to propagate through some values from Time/TimePaths.Mark OLESENMark OLESEN