integration-cfmesh issueshttps://develop.openfoam.com/Community/integration-cfmesh/-/issues2017-09-21T07:15:25Zhttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/1duplicate handling of -patchIds2017-09-21T07:15:25ZMark OLESENduplicate handling of -patchIdsIn mergeSurfacePatches.C lines 352-358 : seems to be minor copy/paste @JureticIn mergeSurfacePatches.C lines 352-358 : seems to be minor copy/paste @Juretichttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/2potential sizing issue for DynList2017-11-04T15:30:15ZMark OLESENpotential sizing issue for DynListNot sure if this is intentional or not. For the constructor
DynListCame(label sz)
will set both the allocated size and the addressable area to be `sz`. The `testDytestDynList.C`
https://develop.openfoam.com/Community/integration-...Not sure if this is intentional or not. For the constructor
DynListCame(label sz)
will set both the allocated size and the addressable area to be `sz`. The `testDytestDynList.C`
https://develop.openfoam.com/Community/integration-cfmesh/blob/port-v1712/testingInterfaces/testDynList/testDynList.C#L40
and https://develop.openfoam.com/Community/integration-cfmesh/blob/port-v1712/testingInterfaces/testDynList/testDynList.C#L50
suggests that this may not be intended (the addressable content being any random junk).
I seem to remember having something similar in a very early incarnation of DynamicList, but this form of the constructor got changed to meaning the same as "reserve allocated space, but start with a zero addressable size".
I did a quick check (by temporarily removing this constructor) and it doesn't seem to be used in too too many places. Nonetheless, it could be worth taking a look at.
@Juretichttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/3problems with 64-bit label-size2018-01-08T13:52:56ZMark OLESENproblems with 64-bit label-sizeI thought they were fixed with 89e12df4e4ecf836123845f9edeb93c29c03eb45, but seems to be something quite a bit worse there. Segfaults included.
I'll leave unassigned for now, but we may need to examine this together.
@JureticI thought they were fixed with 89e12df4e4ecf836123845f9edeb93c29c03eb45, but seems to be something quite a bit worse there. Segfaults included.
I'll leave unassigned for now, but we may need to examine this together.
@Jureticv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/4preparePar does not accept option -decomposeParDict2018-06-28T10:58:48ZRoger AlmenarpreparePar does not accept option -decomposeParDictAs follows:
$ preparePar -help
Usage: preparePar [OPTIONS]
options:
-case <dir> specify alternate case directory, default is the cwd
-decomposeParDict <file>
read decomposePar dicti...As follows:
$ preparePar -help
Usage: preparePar [OPTIONS]
options:
-case <dir> specify alternate case directory, default is the cwd
-decomposeParDict <file>
read decomposePar dictionary from specified location
-fileHandler <handler>
override the file handler type
-noFunctionObjects
do not execute function objects
-parallel run in parallel
-roots <(dir1 .. dirN)>
slave root directories for distributed running
-doc display application documentation in browser
-doc-source display source code in browser
-help print usage information and exit
-help-full print full usage information and exit
Using: OpenFOAM-v1712 (see www.OpenFOAM.com)
Build: v1712
Arch: "LSB;label=32;scalar=64"
$ preparePar -decomposeParDict system/decomposeParDictMesher
...
--> FOAM FATAL ERROR:
cannot find file "/home/ram/projects/consistentOn-b_1nOC/meshTest/system/decomposeParDict"
From function virtual Foam::autoPtr<Foam::ISstream> Foam::fileOperations::uncollatedFileOperation::readStream(Foam::regIOobject&, const Foam::fileName&, const Foam::word&, bool) const
in file global/fileOperations/uncollatedFileOperation/uncollatedFileOperation.C at line 502.
FOAM exiting
Mark OLESENMark OLESENhttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/6OpenFOAM v1806 - cfMesh - Unable to use regular expressions to find and renam...2018-12-21T18:05:31ZPhilippose RajanOpenFOAM v1806 - cfMesh - Unable to use regular expressions to find and rename / refine patchesHello @mark,
There is a problem with cfMesh... A change that you made a couple of months ago breaks the capability of cfMesh to find patches using regular expressions.
That was the reason why I had used stringListOps.H and findStrings...Hello @mark,
There is a problem with cfMesh... A change that you made a couple of months ago breaks the capability of cfMesh to find patches using regular expressions.
That was the reason why I had used stringListOps.H and findStrings in the first place rather than a plain "pick out of a list" option which is what findIndices from listOps.H does (I was the one who put this functionality into cfMesh).
Could you kindly change this back to the original implementation so that regular expressions can be used again?
Thank you.
Regards,
PhilipposeMark OLESENMark OLESENhttps://develop.openfoam.com/Community/integration-cfmesh/-/issues/5compilation source codes of openfoam in windows2020-06-25T09:28:13Zhamiidcompilation source codes of openfoam in windowshello everyone
I want to compile entire library file of openfoam in windows and create a new solver in this but I dont know how it?
can i do it work?
thanks.hello everyone
I want to compile entire library file of openfoam in windows and create a new solver in this but I dont know how it?
can i do it work?
thanks.https://develop.openfoam.com/Community/integration-cfmesh/-/issues/7Meshing the smallest domain in a multi-domain geometry2021-08-09T14:19:48ZBas NieuwboerMeshing the smallest domain in a multi-domain geometry### Functionality to add/problem to solve
Currently it is not possible to mesh the smallest domain in a multi-domain geometry. Cfmesh allways meshes the domain with the largest number of cells. In some cases this is unwanted such as a me...### Functionality to add/problem to solve
Currently it is not possible to mesh the smallest domain in a multi-domain geometry. Cfmesh allways meshes the domain with the largest number of cells. In some cases this is unwanted such as a mesh for the flow between two concentric cylinders. In snappyHexMesh this is solved using the locationInMesh keyword. This is not available in Cfmesh.
### Proposal
Franjo Juretic did implement a basic feature for multi-domain meshing as explained on [cfdonline].
It was pushed to github in a new branch. The commit which enables this is: https://github.com/philippose/cfMesh/commit/7230c449e9a5461a1f0e4aae91bd0117bcd98f26
I’ve implemented this commit in the module of cfMesh for openfoam v2106 and attached the two files that I’ve changed. This allows the use of the keyword: 'allowDisconnectedDomains 1' which is explained in the [cfd online] tread. Problem with this method is that the internal domains are not mapped to the geometry. At least the cellset was not mapped and the resulting mesh using subsetmesh was not snapped to the surface.
As a solution I implemented the keepDomainNumber keyword, which allows you to chose which domain you want to keep. This is not a preferred solution, but it allows you to first visualize all the domains using the allowDisconnectedDomains keyword and in a second attempt mesh the domain number you want to keep.
The best solution would be to implement the locationInMesh keyword. However that is beyond my level to implement.
Using these 2 methods one can view the whole mesh and view the different domains. Then select a single domain using the keepDomainNumber keyword.
### What does success look like, and how can we measure that?
I’ve tested it using an own geometry. One can test it using two concentric cylinders with and without the allowDisconnectedDomains keyword. When enabling the function it should make 2 cell-zones. With the keepDomainNumber keyword you should be able to chose between the two domains.
### Links / references
[cfd online] https://www.cfd-online.com/Forums/openfoam-community-contributions/150500-how-does-cfmesh-determine-region-mesh.html
[checkCellConnectionsOverFaces.C](/uploads/d0d265dbe1ae7ee312685c1afa453ab7/checkCellConnectionsOverFaces.C)
[meshOctreeAddressingCreation.C](/uploads/944475fd0c3ac7102ecd296c65c3229a/meshOctreeAddressingCreation.C)https://develop.openfoam.com/Community/integration-cfmesh/-/issues/8Missing $(LINK_OPENMP) in Make/options2022-12-28T21:09:04ZGabriel GerleroMissing $(LINK_OPENMP) in Make/optionsThe `LIB_LIBS` list in `Make/options` should be changed to also contain a reference to `$(LINK_OPENMP)`. Otherwise, this causes issues when trying to compile and use cfMesh binaries on macOS (in particular, the compiled binaries will fai...The `LIB_LIBS` list in `Make/options` should be changed to also contain a reference to `$(LINK_OPENMP)`. Otherwise, this causes issues when trying to compile and use cfMesh binaries on macOS (in particular, the compiled binaries will fail to dynamically link against OpenMP on launch).
See also: [OpenFOAM issue that introduced the `$(LINK_OPENMP)` definition](https://develop.openfoam.com/Development/openfoam/-/issues/1656), [example of an `options` file that uses `$(LINK_OPENMP)`](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/parallel/decompose/kahipDecomp/Make/options), and [bug report for this issue on OpenFOAM.app (macOS)](https://github.com/gerlero/openfoam-app/issues/88).