openfoam issueshttps://develop.openfoam.com/Development/openfoam/-/issues2023-10-16T16:44:19Zhttps://develop.openfoam.com/Development/openfoam/-/issues/2994Add Allwclean missing (inside some libraries to clean dependencies)2023-10-16T16:44:19ZGabriel Barajasbarajasg@unican.esAdd Allwclean missing (inside some libraries to clean dependencies)### Functionality to add/problem to solve
Add files to clean all the compiled dependencies for each library
### Target audience
OpenFOAM developers
### Proposal
Add the missing cleaning script; For example:
(1) in **transportModels*...### Functionality to add/problem to solve
Add files to clean all the compiled dependencies for each library
### Target audience
OpenFOAM developers
### Proposal
Add the missing cleaning script; For example:
(1) in **transportModels**, create a Allwclean such as:
#!/bin/sh
cd "${0%/*}" || exit # Run from this directory
wclean twoPhaseMixture
wclean interfaceProperties
wclean twoPhaseProperties
wclean incompressible
wclean compressible
wclean immiscibleIncompressibleTwoPhaseMixture
wclean geometricVoF
wcleanLnIncludeAll
#------------------------------------------------------------------------------
(2) or in **thermophysicalModels**, create a Allwclean such as:
#!/bin/sh
cd "${0%/*}" || exit # Run from this directory
wclean specie
wclean solidSpecie
wclean thermophysicalProperties
wclean basic
wclean reactionThermo
wclean laminarFlameSpeed
wclean chemistryModel
wclean barotropicCompressibilityModel
wclean SLGThermo
wclean solidThermo
wclean solidChemistryModel
wclean radiation
wcleanLnIncludeAll
#------------------------------------------------------------------------------
### What does success look like, and how can we measure that?
I am not sure how to measure success, sorry :disappointed:
Thanks,
Gabihttps://develop.openfoam.com/Development/openfoam/-/issues/1622Add a magnitude postOperation to the surfaceFieldValue function object2020-05-01T14:26:01ZJustin GraupmanAdd a magnitude postOperation to the surfaceFieldValue function object### Functionality to add/problem to solve
Sometimes I don't care whether the output from surfaceFieldValue is negative or positive (like when monitoring the sum of the flux). Currently the only postOperation in surfaceFieldValue that ap...### Functionality to add/problem to solve
Sometimes I don't care whether the output from surfaceFieldValue is negative or positive (like when monitoring the sum of the flux). Currently the only postOperation in surfaceFieldValue that appears to be supported is sqrt. Adding other simple ones like mag could be useful.
### Target audience
Anyone who wants the magnitude of the value calculated by surfaceFieldValue
### Proposal
Add a mag postOperation to surfaceFieldValue
### Funding
I'm not prepared to fund this directly, but my guess is this will be useful to others. It just seems odd that only one postOperation is supported.https://develop.openfoam.com/Development/openfoam/-/issues/1057add color values to x3d output2019-07-11T22:13:53ZAdminadd color values to x3d outputI'd like to be able to specify a color profile to be added to the x3d output for isoSurfaces. For example, an isoSurface of fuel fraction can colored by temperature,
```
flame
{
type surfaces;
functionObjectLibs ("libsampling.s...I'd like to be able to specify a color profile to be added to the x3d output for isoSurfaces. For example, an isoSurface of fuel fraction can colored by temperature,
```
flame
{
type surfaces;
functionObjectLibs ("libsampling.so");
enabled true;
writeControl adjustableRunTime;
writeInterval $...animationOutputTime;
interpolationScheme cellPoint;
surfaceFormat x3d;
// Fields to be sampled
fields
(
T
);
surfaces
(
flame
{
type isoSurfaceCell;
isoField ft;
isoValue 0.06;
interpolate true;
regularise false;
}
);
}
```
and have the actual color associated with each temperature value stored within the x3d file. I currently do this by writing out a vtk surface with the corresponding interpolated field, then piping this through pvbatch/pvpython to apply a color profile:
```
# get color transfer function/color map for 'T'
tLUT = GetColorTransferFunction('T')
tLUT.RGBPoints = [291.96875, 0.231373, 0.298039, 0.752941, 1033.3699340820312, 0.865003, 0.865003, 0.865003, 1774.7711181640625, 0.705882, 0.0156863, 0.14902]
# or
tLUT.ApplyPreset('heated_object', True)
```
This creates a cumbersome extra postProcessing step that I'd like to avoid. Ideally the user would be able to specify either a locally saved color profile or a list of RGB points and associated scalar values and then OpenFOAM would directly add the color profile to the x3d output.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2505add coordinate transforms to surface writer output2022-08-19T10:56:52ZMark OLESENadd coordinate transforms to surface writer outputcross-ref EP1886 @martin.werther
Discussed the need to have different locations for the output sampled surface (eg, to relocate into the original car coordinate system and scale in mm).
We already have geometry scaling, but that is mo...cross-ref EP1886 @martin.werther
Discussed the need to have different locations for the output sampled surface (eg, to relocate into the original car coordinate system and scale in mm).
We already have geometry scaling, but that is mostly ad hoc for a few select writers. With this change it would make sense to add in a general cartesian coordsys transform. For example,
```
transform
{
origin (5 1 0);
e1 (0 1 0);
e3 (0 0 1)
}
```
This syntax can also be extended with the `rotation` sub-entry. For example,
```
transform
{
origin (5 1 0);
rotation
{
type euler;
order rollPitchYaw;
angles (0 0 90)
}
}
scale 1000; // [m] -> [mm]
```
These are applied in the OpenFOAM global MKS coordinate system, and the scaling is applied afterwards.v2206Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2701add-debian-repo.sh is hard coded for amd64 architecture2023-03-16T08:12:59ZBen Kenneyadd-debian-repo.sh is hard coded for amd64 architecture### Functionality to add/problem to solve
Hello, I have been experimenting with installing OpenFOAM2112 on arm cpus. I noticed that the `add-debian-repo.sh` script (https://dl.openfoam.com/add-debian-repo.sh) is hardcoded for amd64 but ...### Functionality to add/problem to solve
Hello, I have been experimenting with installing OpenFOAM2112 on arm cpus. I noticed that the `add-debian-repo.sh` script (https://dl.openfoam.com/add-debian-repo.sh) is hardcoded for amd64 but it could easily be updated to support arm64.
### Target audience
Target audience is anybody who is trying to install OpenFOAM on an ARM cpu (like AWS graviton).
### Proposal
In the `add-debian-repo.sh` script (https://dl.openfoam.com/add-debian-repo.sh), replace the hardcoded `amd64` with `$(dpkg --print-architecture)`
For example, change:
```
echo "### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb [arch=amd64] ${repos_url} ${codeName} main" \
> "$apt_source_path"
```
to this
```
echo "### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb [arch=$(dpkg --print-architecture)] ${repos_url} ${codeName} main" \
> "$apt_source_path"
```
### What does success look like, and how can we measure that?
After this update, those who are running on an arm architecture will have the correct repository and can easily install OpenFOAM.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1845add dispatch tags2024-01-11T18:07:45ZMark OLESENadd dispatch tagsfor some places such as `refPtr` it would be useful to support construct read/write as well as construct read-only. However, there is no convenient or reliable means to do so.
Eg,
```
volScalarField fld(...);
refPtr someRef(fld);
```
Sh...for some places such as `refPtr` it would be useful to support construct read/write as well as construct read-only. However, there is no convenient or reliable means to do so.
Eg,
```
volScalarField fld(...);
refPtr someRef(fld);
```
Should this be a const reference or a non-const reference? Currently we only have construct from const-ref since relying on the constness of the supplied argument is fragile at best, or simply wrong.
Propose adding a tagged dispatch constructor. Eg,
```
//- Construct for a non-const reference to an object.
inline refPtr(T& obj, stdFoam::output_t) noexcept;
```
I think that `input_t` and `output_t` might be reasonable enough names (vs read/write) that might be possibly to use elsewhere as well. Would declare in stdFoam.H to make globally available.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/448added to extendedEdgeMesh fails2019-12-09T21:29:28ZMark OLESENadded to extendedEdgeMesh failsextendedEdgeMesh.C
* lines 1270-1273 -> need sublist to handle zero-sized lists (or segfault)
* line 1274: needs `fem.edgeNormals()` to have the correct size for the looping.
@MattijsextendedEdgeMesh.C
* lines 1270-1273 -> need sublist to handle zero-sized lists (or segfault)
* line 1274: needs `fem.edgeNormals()` to have the correct size for the looping.
@MattijsVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1878add face::copyFace method2020-10-13T12:30:50ZMark OLESENadd face::copyFace methodIdea to replace some repetitive code that occurs when collecting faces from various processors (for example).
Existing code:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
face& newF = faces[nFaces++];
newF.resize(f.s...Idea to replace some repetitive code that occurs when collecting faces from various processors (for example).
Existing code:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
face& newF = faces[nFaces++];
newF.resize(f.size());
forAll(f, fp)
{
newF[fp] = f[fp] + nPoints;
}
}
```
With the definition:
```
//- Return a copy of the face with given offset of its labels
inline face copyFace(const label offset) const;
```
This would simplify:
```
for (const face& f : allFaces[Pstream::myProcNo()])
{
faces[nFaces] = f.copyFace(nPoints);
++nFaces;
}
```
Naming similarity to `reverseFace()`Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2958Add -ffp-contract=off for Clang 14 and later2024-03-19T15:07:40ZGuanyang XueAdd -ffp-contract=off for Clang 14 and later### Summary
Clang 14 changed its floating-point behavior. Now the default is `-ffp-contract=on` even with `-O0`
### Steps to reproduce
FMA is enabled by default for Clang 14 and later. This doesn't seem like an issue for x86 (because ...### Summary
Clang 14 changed its floating-point behavior. Now the default is `-ffp-contract=on` even with `-O0`
### Steps to reproduce
FMA is enabled by default for Clang 14 and later. This doesn't seem like an issue for x86 (because of different CPU instructions to do FMA), but for arm64 things like `libsampling` can easily fail.
### Example case
`tutorials/incompressible/simpleFoam/backwardFacingStep2D` leads to infinite loop when running the `sample` function.
### What is the current *bug* behaviour?
A lot of tutorial cases using `libsampling` will be trapped in infinite loop. Any code related to computational geometry may get unexpected results.
### What is the expected *correct* behavior?
The floating-point calculation should strictly follow IEEE-754 to avoid any potential bug that is almost impossible to debug.
### Relevant logs and/or images
https://releases.llvm.org/14.0.0/tools/clang/docs/ReleaseNotes.html#floating-point-support-in-clang
### Environment information
- OpenFOAM version : Any
- Operating system : Any
- Hardware info : Most likely affecting arm64
- Compiler : Clang 14 and later
### Possible fixes
I don't know if it's possible to add flags in wmake rules based on compiler version. I would propose add `-ffp-contract=off` explicitly to the general Clang wmake rule as it doesn't change anything before Clang 13. For `Arm` and `Fujitsu`, it should be added automatically.v2406Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2591add finite-area support to setFields2022-10-26T07:16:47ZMark OLESENadd finite-area support to setFieldscross-ref EP1960cross-ref EP1960Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/3044add flag to not keep comments in foamDictionary and set default behavior to k...2023-12-21T15:52:40Zfranco otaolaadd flag to not keep comments in foamDictionary and set default behavior to keep them### Functionality to add/problem to solve
foamDictionary when using -set or other flags removes all the comments. this makes almost unsable the tool as a lot of us have pieces of code commented that came from other cases and we want to k...### Functionality to add/problem to solve
foamDictionary when using -set or other flags removes all the comments. this makes almost unsable the tool as a lot of us have pieces of code commented that came from other cases and we want to keep. I would propose that the default behavior would be to keep the comments (as people could loose information) and add a flag to not keep them like -removeComments or something in that logic
### Target audience
users in general
### Proposal
detect the comments and place them in between the entries where it was before.
### What does success look like, and how can we measure that?
if we use it for transportProperties for a dictionary that looks like this:
```
transportModel Newtonian;
//[g m s K kgmol A cd]
nu 1e-05; //[0 2 -1 0 0 0 0]
//comment
//comment2
/* block
of
comment
*/
Sct 0.7; //[0 0 0 0 0 0 0]
//comment3
```
that the resulting dictionary at least look like this (with each time that there is a // a new line is created and the /* */ block comments are kept as they were):
```
transportModel Newtonian;
//[g m s K kgmol A cd]
nu 1;//[0 2 -1 0 0 0 0]
//coment
//comment2
/* block
of
comment
*/
Sct 0.7;//[0 0 0 0 0 0 0]
//comment3
```
even if the final structure is not ideal this would be a great addition to using it.https://develop.openfoam.com/Development/openfoam/-/issues/1320add function object to record execution/clock time2019-05-23T10:08:46ZMark OLESENadd function object to record execution/clock time@ivanspisso@ivanspissoMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2044Add Function suggestion: Add Fujitsu-MPI for A64FX.2021-03-31T06:57:59ZTomoki, KaratsuAdd Function suggestion: Add Fujitsu-MPI for A64FX.Hello, @mark.
Thank you for your cooperation in adding the Fujitsu compiler before. This time I would like to add a process to recognize the Fujitsu MPI library on A64FX.
Can I submit the PR this community? If I don't have the right to ...Hello, @mark.
Thank you for your cooperation in adding the Fujitsu compiler before. This time I would like to add a process to recognize the Fujitsu MPI library on A64FX.
Can I submit the PR this community? If I don't have the right to submit a PR, could you incorporate the following fixes?
```
diff --git a/etc/bashrc b/etc/bashrc
index 763f165..a6daac7 100644
--- a/etc/bashrc
+++ b/etc/bashrc
@@ -90,7 +90,7 @@ export WM_COMPILE_OPTION=Opt
# [WM_MPLIB] - MPI implementation:
# = SYSTEMOPENMPI | OPENMPI | SYSTEMMPI | MPI | MPICH | MPICH-GM |
-# HPMPI | CRAY-MPICH | FJMPI | QSMPI | SGIMPI | INTELMPI | USERMPI
+# HPMPI | CRAY-MPICH | FJMPI | FJMPI-A64FX | QSMPI | SGIMPI | INTELMPI | USERMPI
# Specify SYSTEMOPENMPI1, SYSTEMOPENMPI2 for internal tracking (if desired)
# Can also use INTELMPI-xyz etc and define your own wmake rule
export WM_MPLIB=SYSTEMOPENMPI
diff --git a/etc/config.sh/mpi b/etc/config.sh/mpi
index 69617b1..7531cc8 100644
--- a/etc/config.sh/mpi
+++ b/etc/config.sh/mpi
@@ -297,6 +297,15 @@ FJMPI)
_foamAddLib /opt/FJSVpnidt/lib
;;
+FJMPI-A64FX)
+ export FOAM_MPI=fjmpi-a64fx
+ export MPI_ARCH_PATH="$MPI_ROOT"
+
+ export OPAL_PREFIX="$MPI_ARCH_PATH"
+
+ _foamAddPath "$MPI_ARCH_PATH"/bin
+ _foamAddLib "$MPI_ARCH_PATH"/lib64
+ ;;
QSMPI)
export FOAM_MPI=qsmpi
diff --git a/wmake/rules/General/mplibFJMPI-A64FX b/wmake/rules/General/mplibFJMPI-A64FX
index e69de29..6e2ae4f 100644
--- a/wmake/rules/General/mplibFJMPI-A64FX
+++ b/wmake/rules/General/mplibFJMPI-A64FX
@@ -0,0 +1,7 @@
+#------------------------------------------------------------------------------
+
+PFLAGS = -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX
+PINC = -isystem $(MPI_ARCH_PATH)/include/mpi/fujitsu/
+PLIBS = -L$(MPI_ARCH_PATH)/lib64 -lmpi
+
+#------------------------------------------------------------------------------
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/3108Add globalIndex info to globalMeshData2024-03-09T18:31:08ZMark OLESENAdd globalIndex info to globalMeshDataRequested by @Mattijs - replace the total point/face/cell information with globalIndex to allow reuse in various other places without requiring communication each subsequent time.Requested by @Mattijs - replace the total point/face/cell information with globalIndex to allow reuse in various other places without requiring communication each subsequent time.v2406Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1197Add grids to foamMonitor (gnuplot)2019-12-18T16:20:34ZRoger AlmenarAdd grids to foamMonitor (gnuplot)It would be good to add an option to foamMonitor, like "-g|--grid", to plot the background grid to the monitoring plots, so that it is easier to identify the trends and values.
In gnuplot, it is enough to add a "set grid" line to the gnu...It would be good to add an option to foamMonitor, like "-g|--grid", to plot the background grid to the monitoring plots, so that it is easier to identify the trends and values.
In gnuplot, it is enough to add a "set grid" line to the gnuplot file.v1912Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/361Add in architecture checking IOobjects read.2020-01-03T10:00:50ZMark OLESENAdd in architecture checking IOobjects read.Placeholder for topics related to "arch" handling (endian, label and scalar sizes) that was added for v1612.
We now emit arch hints such "LSB,label=32,scalar=64", but don't do anything with them on input.
The first point is to simply to...Placeholder for topics related to "arch" handling (endian, label and scalar sizes) that was added for v1612.
We now emit arch hints such "LSB,label=32,scalar=64", but don't do anything with them on input.
The first point is to simply to check their types on input: "arch" exists and is identical to the current OpenFOAM configuration.
The next would be a special-purpose foam-convert utility. Handling a change from int64 to int32 might only work in very special cases. For example, when snappy needs 64-bit labels because the input surfaces have so many points and faces, but the resulting mesh would still fit with int32.Version v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2677Adding functionobjects/expression to Openfoam v19122023-01-16T00:36:44ZHaitham OsmanAdding functionobjects/expression to Openfoam v1912I have OP v1912 installed on a server. However, expression/fvExpressionField (exprField) utility is NOT installed in the OP v1912. I wonder what is the way to add this feature to OP v1912.
Thanks in advanceI have OP v1912 installed on a server. However, expression/fvExpressionField (exprField) utility is NOT installed in the OP v1912. I wonder what is the way to add this feature to OP v1912.
Thanks in advancehttps://develop.openfoam.com/Development/openfoam/-/issues/1652adding porous media in rotatine zone2022-04-26T16:10:39ZRoshanakadding porous media in rotatine zoneAdding feature of "Relative velocity Resistance formulation" which exists in Ansys-fluent for better prediction of source term when rotating region and porous zone are located in one zone. in Ansys-Fluent, the results, when you choose th...Adding feature of "Relative velocity Resistance formulation" which exists in Ansys-fluent for better prediction of source term when rotating region and porous zone are located in one zone. in Ansys-Fluent, the results, when you choose this option or not selecting it, are quite different.
it seems that Openfoam can only calculate porous source term based on absolute velocity. when it is calculated Darcy-Forchimmier source term based on absolute velocity, it seems that porous zone is fixed in position and not rotating(see attachment files)![Screenshot_from_2020-03-30_10-42-16](/uploads/993db2537153c78ad9347af3ff8f75ad/Screenshot_from_2020-03-30_10-42-16.png)![Screenshot_from_2020-03-30_10-42-32](/uploads/39025939c059c1eb36d8aa33dcaec335/Screenshot_from_2020-03-30_10-42-32.png)v2206Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/2170Add inGroups support for zones2021-09-09T16:15:20ZMark OLESENAdd inGroups support for zonesOne of the topics that has been discussed with @Mattijs is having overlapping zones. This would be convenient for many things, but would also violate a one-to-one mapping that zones currently have.
One possibility would to reuse/refacto...One of the topics that has been discussed with @Mattijs is having overlapping zones. This would be convenient for many things, but would also violate a one-to-one mapping that zones currently have.
One possibility would to reuse/refactor the patchIdentifier for zones and use its inGroup grouping.v2112Mark OLESENMark OLESENhttps://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.