0001265: SnappyHexMesh is not refining features when there are 2 eMesh files (one has a bounding box inside the other one) in parallel

ID	Project	Category	View Status	Date Submitted	Last Update

0001265	OpenFOAM	Bug	public	2014-04-10 14:36	2014-04-25 09:41

Reporter	~~user909~~	Assigned To	~~user4~~
Priority	high	Severity	major	Reproducibility	always
Status	resolved	Resolution	fixed
OS	CentOS	OS Version	Release 6.2

Summary	0001265: SnappyHexMesh is not refining features when there are 2 eMesh files (one has a bounding box inside the other one) in parallel
Description	I am using snappyhexmesh with the refinement features. I have two eMesh files, obtained by surfacefeatureExtract. One eMesh file has its bounding box inside the other one. In fact i am extracting the features with an "insideBox" and an "outsideBox" in the surfacefeatureextractdict. snappyhexmesh is refining up to the level corresponding to the larger bounding box eMesh. So for example, if the eMesh inside has to be refined to level 10 and the eMesh outside to level 3, snappyhexMesh will stop refining when cells get to level 3. in the log file, the number of intersected edges is too low, as if the inside eMesh is not taken into account. The problem only appears in parallel, whatever the decomposition method. In serial it works fine. This bug apppears with release 2.3 (I was using of2.1.1 before and it was working great)
Steps To Reproduce	Create 2 sets of features, with "insideBox" and "outsideBox" and put the 2 eMesh files in the snappy feature refinement step. Only the biggest one (in terms of bounding box) is refined.
Tags	No tags attached.

Date Modified	Username	Field	Change
2014-04-10 14:36	~~user909~~	New Issue
2014-04-22 12:10	~~user4~~	Note Added: 0003019
2014-04-22 12:10	~~user4~~	Status	new => resolved
2014-04-22 12:10	~~user4~~	Fixed in Version	=> 2.3.x
2014-04-22 12:10	~~user4~~	Resolution	open => fixed
2014-04-22 12:10	~~user4~~	Assigned To	=> user4

~~user4~~ 2014-04-22 12:10 ~0003019	I've pushed a fix to 44fcb1216b3ab04c3095027b6d61cff94e0a4159. Could you check on your geometry? If still a problem please re-open the bug. Thanks for reporting.