View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000880 | OpenFOAM | Bug | public | 2013-06-09 03:59 | 2015-02-05 09:26 |
| Reporter | Assigned To | henry | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Platform | Linux | OS | Ubuntu | OS Version | 10.04 |
| Summary | 0000880: bugs in the member function of nbrCoupledPatchID in regionModel class | ||||
| Description | Is the nbrCoupledPatchID function used for find the coupled patchid in the nbrRegion of regionPatchI in current region? If it is so, it seems that we should get the primaryPatchName directly rather than geting the sampling patch using mappedPatchBase, the sampling patch of current patch should be the neighbor patch name. That is the following code in line 289-line 296 in regionModel.C should be changed to const word& primaryPatchName = regionMesh().boundryMesh()[regionPatchI].name(); or get the neighbor patch name directly but not use samplePatch. One use samplePatch and one get the patch name directly, but not both use samePatch in a word. regards, Junwei | ||||
| Tags | No tags attached. | ||||
|
|
Yes, this is function is used to get the nbrPatchI using the nbrRegion and the localPatchId. The coupled pathes are mappedPatchBase and the function asks on both sides which is the name of the patch being sampled, if they are similar it returns the ID. In this way the search is consistent on both side. The way you propose is another alternative as well. Regards |
