View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002482OpenFOAMBugpublic2017-03-01 09:402017-03-05 12:33
Reporterzarox Assigned Tohenry  
PrioritylowSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformGNU/LinuxOSUbuntuOS Version14.04
Summary0002482: Tutorial movingCone error with missing patch boundary initialization
DescriptionThe tutorial can't work, as axis patch is missing in 0 for U ,p ,pointMotionUx. I add axis as a symmetryPlane and that fix the issue. I checked the OpenFOAM-dev git repository and the issue would arrive too.
TagsNo tags attached.

Activities

henry

2017-03-01 10:04

manager   ~0007832

I just tested OpenFOAM-dev/tutorials/incompressible/pimpleDyMFoam/movingCone which runs fine.

henry

2017-03-01 10:06

manager   ~0007833

Runs fine in OpenFOAM-4.x as well.

zarox

2017-03-01 10:23

reporter   ~0007834

I attached a screenshot of the error. The axis patch is define in the BlockMeshDict and so in the polyMesh/boundary but not in the 0/ U, p, point Motion. I don't get why I have the error and not you. As, I use the OpenFOAM-4.1 and I checked the same axis patch exist in the dev git repository.
patchField_axis.png (41,859 bytes)   
patchField_axis.png (41,859 bytes)   

henry

2017-03-01 10:32

manager   ~0007835

blockMesh removes the axis because it is defined in the blockMeshDict to have duplicate points, hence zero area and can be removed. There appears to be a problem with the blockMesh version you are using if it is not removing the axis.

I am unable to reproduce the error here, the movingCone case runs as expected for all OpenFOAM installations I have and have ever had.

zarox

2017-03-01 11:44

reporter   ~0007836

Ok. Sorry for the disturbance. I will check the blockMesh version.

MattijsJ

2017-03-03 09:56

reporter   ~0007853

The axis patch itself does not actually disappear. It just has 0 faces. What makes it work is automatic handling for 'empty' patches when reading a field - if there are no patchFields for an empty patch it will automatically construct an emptyFvPatchField for it. (see GeometricBoundaryField.C line 135)

Issue History

Date Modified Username Field Change
2017-03-01 09:40 zarox New Issue
2017-03-01 10:04 henry Note Added: 0007832
2017-03-01 10:06 henry Note Added: 0007833
2017-03-01 10:23 zarox File Added: patchField_axis.png
2017-03-01 10:23 zarox Note Added: 0007834
2017-03-01 10:32 henry Note Added: 0007835
2017-03-01 11:44 zarox Note Added: 0007836
2017-03-03 09:56 MattijsJ Note Added: 0007853
2017-03-05 12:33 henry Assigned To => henry
2017-03-05 12:33 henry Status new => closed
2017-03-05 12:33 henry Resolution open => unable to reproduce