Development issueshttps://develop.openfoam.com/groups/Development/-/issues2016-08-09T09:07:09Zhttps://develop.openfoam.com/Development/openfoam/-/issues/167Ensight surface writer does not write fields2016-08-09T09:07:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comEnsight surface writer does not write fields[controlDict](/uploads/e630334b702cd7862e986783a5cc2f2e/controlDict)
I'm running cavity with attached controlDict. It writes Ensight files to postProcessing/ but these are not referenced in the .case file so never loaded. (I think)
[controlDict](/uploads/e630334b702cd7862e986783a5cc2f2e/controlDict)
I'm running cavity with attached controlDict. It writes Ensight files to postProcessing/ but these are not referenced in the .case file so never loaded. (I think)
Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/212"Current Release" links are broken in some of the side menus2016-08-18T10:16:53ZAdmin"Current Release" links are broken in some of the side menusThe following pages still refer to the v3.0+ on the side menu:
* http://openfoam.com/download/install-source.php
* http://openfoam.com/download/installation.php
* http://openfoam.com/download/install-binary.php
* http://ope...The following pages still refer to the v3.0+ on the side menu:
* http://openfoam.com/download/install-source.php
* http://openfoam.com/download/installation.php
* http://openfoam.com/download/install-binary.php
* http://openfoam.com/download/install-windows.php
* http://openfoam.com/download/release-history.php
* http://openfoam.com/download/index.php
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/221renumberMesh doesn't work2016-08-26T05:29:46ZAdminrenumberMesh doesn't workI want to solve the DTC-Hull in interFoam solver with another ship. all the commands in allrun file work properly except "renumberMesh" with the following error.![Screenshot_from_2016-08-25_03-17-23](/uploads/16343e9389fbea7cd23573c74692...I want to solve the DTC-Hull in interFoam solver with another ship. all the commands in allrun file work properly except "renumberMesh" with the following error.![Screenshot_from_2016-08-25_03-17-23](/uploads/16343e9389fbea7cd23573c746927bbc/Screenshot_from_2016-08-25_03-17-23.png)https://develop.openfoam.com/Development/openfoam/-/issues/236link/compilation error2016-09-19T05:32:30ZAdminlink/compilation errorI have got a compilation error on my Linux (Suse tumbleweed) machine (all the environmental variables are set correctly , etc.)
/home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/src/finiteVolume/fields/fvsPatchField...I have got a compilation error on my Linux (Suse tumbleweed) machine (all the environmental variables are set correctly , etc.)
/home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/src/finiteVolume/fields/fvsPatchFields/basic/calculated/calculatedFvsPatchFields.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
make: *** [/home/walter/OpenFOAM/OpenFOAM-v1606+/wmake/makefiles/general:157: /home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/lib/libfiniteVolume.so] Error 1
Any clues ?
Thank You.https://develop.openfoam.com/Development/openfoam/-/issues/237Instructions that refer to the cavity case need to be updated2016-09-28T16:27:29ZAdminInstructions that refer to the cavity case need to be updatedI haven't checked them all, but at least the following two pages need updating:
* http://www.openfoam.com/download/install-windows.php
* http://www.openfoam.com/download/install-binary.php
The reason is that the tutorial `incompress...I haven't checked them all, but at least the following two pages need updating:
* http://www.openfoam.com/download/install-windows.php
* http://www.openfoam.com/download/install-binary.php
The reason is that the tutorial `incompressible/icoFoam/cavity` is now a group of cases and not a single case. You have at least two possibilities:
* Use the path `incompressible/icoFoam/cavity/cavity`
* Use the `Allrun` script, instead of `blockMesh`+`icoFoam`
For more details: http://bugs.openfoam.org/view.php?id=2149#c6527
----
Side note: I only spotted this while trying to answer a question on the forum: http://www.cfd-online.com/Forums/openfoam-installation/176161-openfoam-plus-v1606-compiling-installing-problems-2.html#post618348AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/214Typo in 'SunDirTraking'2016-09-28T17:27:10ZAdminTypo in 'SunDirTraking'This is by no means critical, but `SunDirTraking` has a typo, since it's missing the `c` in `Tracking`, i.e. it should be `SunDirTracking`.
The files that have these typos can be found with the following commands:
```
grep -r 'Sun...This is by no means critical, but `SunDirTraking` has a typo, since it's missing the `c` in `Tracking`, i.e. it should be `SunDirTracking`.
The files that have these typos can be found with the following commands:
```
grep -r 'SunDirTraking' applications src tutorials
grep -r 'sunDirTraking' applications src tutorials
```
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/211The + sign in "OpenFOAM-v1606+" leads to a non-breaking error when building t...2016-09-30T10:47:52ZAdminThe + sign in "OpenFOAM-v1606+" leads to a non-breaking error when building the "PVReaders" plug-ins for ParaViewWhen building "OpenFOAM-v1606+" from source code, the following error appears when building `$FOAM_UTILITIES/postProcessing/graphics/PVReaders/PVblockMeshReader/PVblockMeshReader`:
```
[ 5%] Generating Documentation HTMLs from xmls
...When building "OpenFOAM-v1606+" from source code, the following error appears when building `$FOAM_UTILITIES/postProcessing/graphics/PVReaders/PVblockMeshReader/PVblockMeshReader`:
```
[ 5%] Generating Documentation HTMLs from xmls
Error FODC0002 in file:///home/ofuser/OpenFOAM/OpenFOAM-v1606: Error opening /home/ofuser/OpenFOAM/OpenFOAM-v1606: No such file or directory
Error FODC0002 in file:///applications/utilities/postProcessing/graphics/PVReaders/PVblockMeshReader/PVblockMeshReader/PVblockMeshReader_SM.xml: Error opening /applications/utilities/postProcessing/graphics/PVReaders/PVblockMeshReader/PVblockMeshReader/PVblockMeshReader_SM.xml: No such file or directory
```
The reason why this happens is because the `+ ` symbol is used as a path separator for the variable `input_xmls` in `ThirdParty-v1606+/platforms/linux64Gcc/ParaView-5.0.1/lib/cmake/paraview-5.0/generate_proxydocumentation.cmake`.
This isn't a problem when building from the git repository, given that `WM_PROJECT_VERSION=plus`.
----
Either way, I unfortunately haven't figured out a workaround for this. But as I've stated in the title, this is non-breaking error, i.e. it will still build without stopping.
https://develop.openfoam.com/Development/openfoam/-/issues/169Unsigned versions have the same pTraits limits as their signed counterparts.2016-10-01T08:53:50ZMark OLESENUnsigned versions have the same pTraits limits as their signed counterparts.In uint32.C, uint64.C:
const uint64_t Foam::pTraits<uint64_t>::min = INT64_MIN;
const uint64_t Foam::pTraits<uint64_t>::max = INT64_MAX;
const uint32_t Foam::pTraits<uint32_t>::min = INT32_MIN;
const uint32_t Foam...In uint32.C, uint64.C:
const uint64_t Foam::pTraits<uint64_t>::min = INT64_MIN;
const uint64_t Foam::pTraits<uint64_t>::max = INT64_MAX;
const uint32_t Foam::pTraits<uint32_t>::min = INT32_MIN;
const uint32_t Foam::pTraits<uint32_t>::max = INT32_MAX;
STYLE:
uLabel.H includes the zero-sized file `uLabelSpecific.H`, which should be removed as clutter.
Also reported on mantis as http://bugs.openfoam.org/view.php?id=2137
@Mattijshttps://develop.openfoam.com/Development/openfoam/-/issues/42paraview-4.4.0 install produces lib/paraview-3.0/, include/paraview-3.0 (inst...2016-10-01T08:55:40ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview-4.4.0 install produces lib/paraview-3.0/, include/paraview-3.0 (instead of lib/paraview-4.4)The ./CMake/ParaViewDetermineVersion.cmake does a 'git describe' to find the current Paraview version. This recurses up and finds the ThirdParty/.git where 'git-describe' returns
version-3.0.0-7-g1e6453d
This path gets used to vers...The ./CMake/ParaViewDetermineVersion.cmake does a 'git describe' to find the current Paraview version. This recurses up and finds the ThirdParty/.git where 'git-describe' returns
version-3.0.0-7-g1e6453d
This path gets used to version the resulting files.
Workaround: build paraview not under a ThirdParty with a git. Or rename the resulting install directories.https://develop.openfoam.com/Development/openfoam/-/issues/242Reconstruct problem for Qro scalarField with libs in controlDict2016-10-03T22:16:38ZAdminReconstruct problem for Qro scalarField with libs in controlDictI'm using version OF-plus from 13 July 2016 (plus-5d9038294daa). I need to add a new radiation library to controlDict file. But even if I add the original libradiationModels.so this problem appears:
When the volScalarField Qr is recon...I'm using version OF-plus from 13 July 2016 (plus-5d9038294daa). I need to add a new radiation library to controlDict file. But even if I add the original libradiationModels.so this problem appears:
When the volScalarField Qr is reconstructed, the scalarField Qro is filled with non-zero values despite its original value is 'uniform 0'.
Till now I have observed that:
* If no library is included in controlDict file, this error does not appear.
* If I add the library but without the NamedEnum definition (and proper .C modifications) in file submodels/boundaryRadiationProperties/boundaryRadiationPropertiesPatch.C, this problem does not appear.
* If I use OF-dev this problem does not appear.
I attach a case to reproduce the error [possibleBugReconstruct.tar.gz](/uploads/3210d3d305fe453710186e944f8d46f1/possibleBugReconstruct.tar.gz). The steps to reproduce it are:
1. extract files from possibleBugReconstruct.tar.gz
2. ./Allrun-parallel
3. reconstructPar -allRegions -time 10
4. vim 10/left/Qr (and check for Qro field)Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/229ENH: add option to surfaceCheck to make optional writing of OBJ files2016-10-04T09:40:51ZPrashant SonakarENH: add option to surfaceCheck to make optional writing of OBJ filesRequested at EP#254
A low quality input geometry could produce thousand's or more error element OBJs.
It would be nice to make such file writing optional.
@markRequested at EP#254
A low quality input geometry could produce thousand's or more error element OBJs.
It would be nice to make such file writing optional.
@markVersion v1612Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/249Field construct from indirect list2016-10-04T09:50:10ZMark OLESENField construct from indirect listCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/274BUG: single locationInMesh behavior now broken when compared with the foundat...2016-10-18T05:05:13ZAdminBUG: single locationInMesh behavior now broken when compared with the foundation codeThe single locationInMesh behavior is now broken when there is a geometry based cellZone defined when compared to the foundation code.
I've attached 3 pics and the model. The geometry pic is a pipe with a cellZone geometry defined in t...The single locationInMesh behavior is now broken when there is a geometry based cellZone defined when compared to the foundation code.
I've attached 3 pics and the model. The geometry pic is a pipe with a cellZone geometry defined in the middle.
![geometry](/uploads/80450e9dd316c13340de821bbaf3fd13/geometry.PNG)
The "3.0.x_mesh_with_cellZone.png" pic is what foundation version 3.0.x produces when a single locationInMesh is defined to one side of the cellZone. 3.0.x correctly sets the middle to one cellZone and the rest of the pipe to defaultFaces.
![3.0.x_mesh_with_cellZone](/uploads/91dace921e83fe4d3c8fc443c9663e92/3.0.x_mesh_with_cellZone.PNG)
The "v1606_mesh_with_cellZone_broken.PNG" shows what v1606 produces using the same model. It cuts off half the pipe and then leaks out into the background mesh. Not cool.
![v1606_mesh_with_cellZone_broken](/uploads/2e937dd4d15eebf0371ec383085e0347/v1606_mesh_with_cellZone_broken.PNG)
I know there has been a lot of changes so if I'm missing something let me know. I have tested the locationsInMesh functionality and that works OK for this model, but the single locationInMesh fails. I've attached the model.
[mesh_issue.tar.gz](/uploads/3f1f0af8bf58b7d1b42746861e3892d9/mesh_issue.tar.gz)https://develop.openfoam.com/Development/openfoam/-/issues/258paraview plugin not being built in merged version2016-10-24T21:17:05ZMark OLESENparaview plugin not being built in merged versionchange in logic with config changechange in logic with config changeMark OLESENMark OLESEN2016-10-04https://develop.openfoam.com/Development/openfoam/-/issues/183ENH: extend coverage for wmUNSET2016-10-24T21:19:11ZPrashant SonakarENH: extend coverage for wmUNSETCertain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Certain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/277sed: -e expression #1, char 72: unknown option to `s' ( And some funky PATH e...2016-10-29T08:39:43ZAdminsed: -e expression #1, char 72: unknown option to `s' ( And some funky PATH errors )```
[ steven.walton ] [~] > lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
```
I am also on a domain controlled computer.
When sourcing `/opt/openfoa...```
[ steven.walton ] [~] > lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
```
I am also on a domain controlled computer.
When sourcing `/opt/openfoam4/etc/bashrc` and opening a new bash terminal I get the following error
```
sed: -e expression #1, char 72: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
bash: uname: No such file or directory
Your "" operating system is not supported by this release
of OpenFOAM. For further assistance, please contact www.OpenFOAM.org
Command 'sed' is available in '/bin/sed'
Command 'mpicc' is available in '/usr/bin/mpicc'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
The command could not be located because '/bin' is not included in the PATH environment variable.
mpicc: command not found
sed: command not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
bash: sed: No such file or directory
/opt/openfoam4/bin/foamCleanPath: 129: /opt/openfoam4/bin/foamCleanPath: sed: not found
```
The worse part of this is that `PATH` gets completely overwritten!
I can fix some of this by getting rid of line 154 in `/opt/openfoam4/etc/bashrc`. That reduces to the following error
```
sed: -e expression #1, char 72: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
```
If I am running in zsh (yes, I know it says bashrc) I get
```
sed: -e expression #1, char 72: unknown option to `s'
/opt/openfoam4/etc/config.sh/aliases:73: bad option: -t
```
If I enter bash and type `wmRefresh` it overwrites `PATH` and I now have no access to simple commands like `ls`. ( Removing the `-t` in that line reduces the last error in zsh but adds the line `bash: type: wmRefresh: not found` into the list of errors for bash.) Which is strange because the comment above line 73 in `/opt/openfoam4/etc/config.sh/aliases` says `For backward-compatibility unalias wmRefresh if it is defined as an alias`.
Working through this one I see that `which wmRefresh` and `alias wmRefresh` return nothing. So getting the same behaviour in both shells ( and a lack of care for backwards compatibility at this point ) I found that I could just remove lines 74-80 in `/opt/openfoam4/etc/config.sh/aliases`. Note that if I just removed line 73 bash would have `PATH` overwritten again ( **why ever modify `PATH` when we have other environment variables?** ).
So at this point I am only left with the sed errors ( 1 in zsh and 3 in bash ). I cannot tell that I am getting any errors* in using OpenFoam, but as you might imagine it is quite annoying seeing multiple errors every time I open a new shell. I have been attempting to resolve these issues by looking at where `sed` has been used, but I'm not seeing a problem. It doesn't appear to be a `sed` command within `/opt/openfoam4/etc`, and grepping a directory back results is quite a log of commands.
So I am wondering if anyone else has had this error and solved it.
*To check validity through modifications I am just run the cavity icoFoam case, checking for the known solution.https://develop.openfoam.com/Development/openfoam/-/issues/262Absolute third-party paths in wmkdep, possible false positive on sed2016-11-07T06:27:23ZMark OLESENAbsolute third-party paths in wmkdep, possible false positive on sedAlso reported as http://bugs.openfoam.org/view.php?id=2283
In the wmake rules 'transform', the sed expression is missing a beginning anchor and a trailing slash , which makes it slightly susceptible to a false substitutions.
Additional...Also reported as http://bugs.openfoam.org/view.php?id=2283
In the wmake rules 'transform', the sed expression is missing a beginning anchor and a trailing slash , which makes it slightly susceptible to a false substitutions.
Additionally, any dependencies within ThirdParty retain their absolute path and are not resolved to `$WM_THIRD_PARTY_DIR`.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/291BUG: decaying isotropic turbulence case2016-11-07T06:27:32ZPrashant SonakarBUG: decaying isotropic turbulence casePlaceholder to revisit boxTurb for decaying isotropic turbulence case, which doesn't seem to give correct results.
(From EP#262)Placeholder to revisit boxTurb for decaying isotropic turbulence case, which doesn't seem to give correct results.
(From EP#262)Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/22Discussion: patchProbes compatibility with fixedLocations2016-11-07T14:27:03ZPrashant SonakarDiscussion: patchProbes compatibility with fixedLocationsStandard probes FO has additional entry
// Optional: do not recalculate cells if mesh moves
fixedLocations false;
Is this also applicable for patchProbes?
@andy Standard probes FO has additional entry
// Optional: do not recalculate cells if mesh moves
fixedLocations false;
Is this also applicable for patchProbes?
@andy Functionality migration from internal development lineMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/286STYLE: Duplicate information in SHM reference dict2016-11-09T11:52:36ZPrashant SonakarSTYLE: Duplicate information in SHM reference dict```
// Optional: keep zero-sized patches. By default snappyHexMesh filters
// these out.
//keepPatches true; // default false
//Optional: preserve all generated patches. Default is to remove
// zero-sized patches....```
// Optional: keep zero-sized patches. By default snappyHexMesh filters
// these out.
//keepPatches true; // default false
//Optional: preserve all generated patches. Default is to remove
// zero-sized patches.
//keepPatches true;
```
in applications/utilities/mesh/generation/snappyHexMesh/snappyHexMeshDictVersion v1612AdminAdmin