View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003406 | OpenFOAM | Feature | public | 2019-12-04 17:22 | 2019-12-05 11:48 |
| Reporter | michael.mueller-wrd | Assigned To | henry | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | Linux | OS | centOS | ||
| Summary | 0003406: paraFoam -builtin fails in case of not having ascending order of boundary entries | ||||
| Description | I came across this issue while I modified the constant/REGIONs/polyMesh/boundary files via scripting, in order to generate an automated case setup for chtMultiRegioncases. For multi region cases, we have to use the reader: paraFoam -builtin The boundary entries in constant/REGIONs/polyMesh/boundary include the number of startFace. In case that the listing in the boundary file is not conform with the numbering of startFace, paraFoam -builtin will not work for this region and it will be lost in paraview. I also checked single region cases: same outcome for paraFoam -builtin if listing is not in ascending order. If I use the plain paraFoam reader (w/o -builtin flag), the mesh or case will be shown regardless of the order of the entries in constant/polyMesh/boundary. | ||||
| Steps To Reproduce | use any chtMultiRegionFoam tutorial case: 1. check paraFoam -builtin after meshing to view case => OK 2. switch order e.g. of 1st and 2nd entry of constant/REGION/polyMesh/boundary to 2nd, 1st... 3. check paraFoam -builtin after meshing to view case => REGION is lost use any simpleFoam tutorial case: 1. check paraFoam -builtin after meshing to view case => OK 2. switch order e.g. of 1st and 2nd entry of constant/polyMesh/boundary to 2nd, 1st... 3. check paraFoam -builtin after meshing to view case => fails repeat simpleFoam test with plain paraFoam... | ||||
| Additional Information | I do not know if you are aware of this issue. I was not... Of course, I may take care of not messing up the order of boundary entries while processing the files. But maybe other users run into this issue, too. So, it would be great if you could take a look into the builtin reader and adjust it accordingly... Thanks a lot! Michael | ||||
| Tags | No tags attached. | ||||
|
|
We are not involved in the development or maintenance of the OpenFOAM reader provided by KitWare; we maintain a general and up to date reader with OpenFOAM and recommend that you use that. |
|
|
Thanks, then the recommended procedure would be to use paraFoam -touchAll and then load all region files (*.OpenFOAM) separately in to paraview... |
|
|
Yes that is what we use what we want to view all the regions at the same time but generally we view the regions separately. |
|
|
The issue reported relates to code developed and maintained by KitWare. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-12-04 17:22 | michael.mueller-wrd | New Issue | |
| 2019-12-04 17:34 | henry | Note Added: 0010957 | |
| 2019-12-05 09:05 | michael.mueller-wrd | Note Added: 0010958 | |
| 2019-12-05 09:42 | henry | Note Added: 0010959 | |
| 2019-12-05 11:48 | henry | Assigned To | => henry |
| 2019-12-05 11:48 | henry | Status | new => closed |
| 2019-12-05 11:48 | henry | Resolution | open => no change required |
| 2019-12-05 11:48 | henry | Note Added: 0010963 |
