Ivar KJELBERG
COMSOL Multiphysics(r) fan, retired, former "Senior Expert" at CSEM SA (CH)
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
2012年1月23日 GMT-5 07:18
Hi
the intersection of almost adjacent spheres or circles in 2D, is always topologically delicate, you have silver fillets and other issues. Also I suspect tat the internal COMSOL graphics driver is not as good as the higher quality CAD driver of the most advanced (and far expensiver) tools.
Turn on the transparency you will see part of the mesh inside too
I.e. in your Advanced geometry, open the selection list view, then activate domain and scan through your domains, compare it to the standard diamond:
you will see some extra domains, coming from the intersection, and perhaps also from your resolution settings, such as 9,10,11,12, 17,18,19,20, 23,24,25,26, 32,33,34,35,36 these are very small, they might even overlap, and will produce thousand of fine elements, including forcing the rest of the connecting mesh to be very dense, for nothing, I believe.
and deleting them might just give you a hole in your geometry, neither not acceptable.
I do not see any easy way out, perhaps try with a CAD tool and import the shape to COMSOL, or change the way you make differences in COMSOL
Do not forget that you can make multiple copies/moves in one go (of an object, by defining an array in the x,y,z entries)
--
Good luck
Ivar
Hi
the intersection of almost adjacent spheres or circles in 2D, is always topologically delicate, you have silver fillets and other issues. Also I suspect tat the internal COMSOL graphics driver is not as good as the higher quality CAD driver of the most advanced (and far expensiver) tools.
Turn on the transparency you will see part of the mesh inside too
I.e. in your Advanced geometry, open the selection list view, then activate domain and scan through your domains, compare it to the standard diamond:
you will see some extra domains, coming from the intersection, and perhaps also from your resolution settings, such as 9,10,11,12, 17,18,19,20, 23,24,25,26, 32,33,34,35,36 these are very small, they might even overlap, and will produce thousand of fine elements, including forcing the rest of the connecting mesh to be very dense, for nothing, I believe.
and deleting them might just give you a hole in your geometry, neither not acceptable.
I do not see any easy way out, perhaps try with a CAD tool and import the shape to COMSOL, or change the way you make differences in COMSOL
Do not forget that you can make multiple copies/moves in one go (of an object, by defining an array in the x,y,z entries)
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
2012年1月23日 GMT-5 07:49
Thanks for your answer. I didn't find the selection list "view" but thanks for telling me where the problem lies. One way out you suggested is to change the way I make differences in COMSOL. What exactly do you mean by this suggestion?
Also thanks for the tip with the copy operations.
Thanks for your answer. I didn't find the selection list "view" but thanks for telling me where the problem lies. One way out you suggested is to change the way I make differences in COMSOL. What exactly do you mean by this suggestion?
Also thanks for the tip with the copy operations.
Ivar KJELBERG
COMSOL Multiphysics(r) fan, retired, former "Senior Expert" at CSEM SA (CH)
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
2012年1月23日 GMT-5 09:16
Hi
try the Alt V "Selection list"
or select from the main window File - Edit => "View" button
sometimes you get different results depending on the order you subtract objects, I expect it's related to the sizes and some kind of tolerances adjustment based on sizes, it seems to be there at least for very large size ratio objects. But I haven't investigated it in detail
--
Good luck
Ivar
Hi
try the Alt V "Selection list"
or select from the main window File - Edit => "View" button
sometimes you get different results depending on the order you subtract objects, I expect it's related to the sizes and some kind of tolerances adjustment based on sizes, it seems to be there at least for very large size ratio objects. But I haven't investigated it in detail
--
Good luck
Ivar