View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002529||OpenFOAM||Bug||public||2017-04-20 10:44||2018-07-10 11:24|
|Fixed in Version||dev|
|Summary||0002529: triSurfaceMesh in blockMesh|
I noticed that triSurfaceMesh is selectable in the new blockMesh extension (projection) in OpenFOAM-dev, So I tried to test it. triSurfaceMesh is looking for the stl file in constant/geometry instead of constant/triSurface which isn't typical in OpenFOAM. I'm not sure if this behaviour is intended or not.
|Steps To Reproduce||1) Use blockMesh/pipe tutorial|
2) Modify geometry.cylinder dict to
//point1 (0 -4 0);
//point2 (0 4 0);
3) Add constant/triSurface/cylinder.stl file.
|Additional Information||The problem is this function; |
const IOobject& io,
const dictionary& dict
In particular, fName = io.objectPath().path()/fName;
The "io.objectPath().path()" is pointing to /geometry not /triSurface.
If this behaviour is intended, it worth to be mentioned in the class description at least.
||The issue is that blockMesh can work with any form of searchableSurfaces, not just triSurfaceMesh and the location is specified as /geometry irrespective of the form of searchableSurface is provided. If the directory name were changed to /triSurface it would be odd for the other current and future forms of searchableSurface supported. The anomaly is that /triSurface is used elsewhere in OpenFOAM for reading searchableSurfaces even though they might not be triSurfaces but some other form of searchableSurface. If we were to make any change for consistency it would have to be /triSurface -> /geometry rather than the other way round.|
||I totally agree,/geometry is the general consistent way to procedure. But for now, keeping searchableExtrudedCircle reads from /triSurface is confusing. Additionally, I think searchableExtrudedCircle should be moved src/meshTools/searchableSurface.|
||Agreed, I will make the changes to searchableExtrudedCircle you suggest.|
||searchableExtrudedCircle cannot be put in src/meshTools/searchableSurface because it depends on edgeMesh which depends on meshTools. I can put it in edgeMesh but this is not very logical.|
||I can see the problem now, it means the only way would be moving searchableSurface + searchableExtrudedCircle to another point after edgeMesh. Maybe to src/mesh but I'm not sure if that is logical or not. what do you think?|
||searchableExtrudedCircle can either be in the edgeMesh library or another compiled after the edgeMesh library or in a new library. src/mesh is not a library, it contains the directory for the blockMesh extrudeModel snappyHexMesh libraries but could hold yet another library for the searchableSurfaces.|
Yes, that what I mean searchableSurfaces as library but not directly in src because it belongs to mesh in some sense but does not belongs too much to edgeMesh.
Regarding your latest commit, blockMesh/pipe/ tutorial will require small modification (moving triSurface -> geometry ).
||I am not keen on creating yet another mesh library, I think it would be better to merge edgeMesh into meshTools and rename meshTools to something more logical.|
||I think, that will be very sensible as well|
Resolved by commits:
|2017-04-20 10:44||hk318i||New Issue|
|2017-04-20 10:44||hk318i||Tag Attached: blockMesh|
|2017-04-20 10:44||hk318i||Tag Attached: openfoam-dev|
|2017-04-20 10:58||henry||Note Added: 0008034|
|2017-04-20 11:13||hk318i||Note Added: 0008036|
|2017-04-20 11:21||henry||Note Added: 0008037|
|2017-04-20 12:00||henry||Note Added: 0008038|
|2017-04-20 12:34||hk318i||Note Added: 0008039|
|2017-04-20 12:39||henry||Note Added: 0008040|
|2017-04-20 12:44||hk318i||Note Added: 0008041|
|2017-04-20 12:50||henry||Note Added: 0008042|
|2017-04-20 14:25||hk318i||Note Added: 0008043|
|2017-04-21 10:40||henry||Assigned To||=> henry|
|2017-04-21 10:40||henry||Status||new => resolved|
|2017-04-21 10:40||henry||Resolution||open => fixed|
|2017-04-21 10:40||henry||Fixed in Version||=> dev|
|2017-04-21 10:40||henry||Note Added: 0008044|
|2018-07-10 11:24||administrator||Tag Detached: openfoam-dev|