<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Hi Dan,<br>What is your configuration? Did you build cgm with OpenCascade or with Cubit/Acis?<br>I think it is OpenCascade. <br>So are you trying to associate all mesh vertices with the closest surface geometry?<br>Can you send the code you are using to test this? <br><br>iBase_REGION corresponds to a volume entity in iGeom or to a 3D solid element in iMesh (3D topological entity)<br><br>From what I see, the geometry and mesh are pretty close to each other. How are you deciding what nodes are on the boundary? Are you using Skinner in moab?<br><br>Iulian<br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">
Hi,<br>
I'm still trying to test the relation between mesh and geometric
model. But there is some problem, when I try to use iGeom
(iGeom_getEntClosestPt) to compute<br>
the distance from mesh coordinates and geom surfaces.<br>
There 2 point which should be on geometric surface, but the computed
distance are wrong:<br>
10990.6 2573.73 0 (computed closest:11202.6 2486.35 0.000607243) <br>
10990.6 2573.73 3000 (-->11202.6 2486.36 3000)<br>
There 're no problem by other points (in ori_mesh.vtk). <br>
I wonder what happened by the computing. And how exactly does
iGeom_getEntClosestPt work?<br>
Best Regards<br>
Le, Dan<br>
<br>
PS: what's the meaning of iBase_REGION ?<br>
<br>
Am 16.12.2011 06:39, schrieb Iulian Grindeanu:
<blockquote cite="mid:1453120619.73369.1324013942825.JavaMail.root@zimbra.anl.gov">
<style>p { margin: 0; }</style>
<div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);"><br>
<blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">
<div id="DWT823" style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);">Mesquite will modify
position of the free nodes, to get a better quality;
"constrained nodes" can be constrained on geometry entity,
so they can move only along geometry. This is an advanced
use of Mesquite, and you should understand what you can do
with it. <br>
<br>
Sets of nodes can be constrained to move along geometry; 1d
sets for geometric edges, 2d sets for faces (while keeping
the boundary nodes on specific boundary edges too).<br>
This setup may have to be done "by hand", including
generation of sets. How did you create the hexa mesh? The
nodes that are on the boundary may have to be put in sets,
for all your edges, faces, etc. <br>
You have a unit issue with your model; I think that in
theory you can "squeeze" that vtk file to fit that wall
geometry, but I do not think that this is the proper way to
use mesquite. This is why I suggested to look at meshkit
examples (only one mesquite test involves geometry, and it
is too simple)<br>
<br>
One would be test_onetooneswept in meshkit/test/algs.<br>
<br>
Iulian<br>
<br>
</div>
</blockquote>
I was wrong with the suggestion to try test_onetooneswept in
meshkit/test/algs.<br>
Until this evening, it did not work with OpenCascade;<br>
It should work now, if you update MeshKit<br>
Also, in Lasso, test_entset will work if you launch it with<br>
test_ent brick.stp brick.h5m (update Lasso too, to get those
files)<br>
<br>
Iulian<br>
<br>
<br>
</div>
</blockquote>
<br>
</blockquote><br></div></body></html>