Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.
boundary "not applicable"
Posted 2010/09/21 13:37 GMT-4 2 Replies
Please login with a confirmed email address before reporting spam
I'm building a 2D model of a rectangular tube filled with water and open ends as well as a middle moving boundary. Therefore I'm using Navier-Stokes application and moving mesh application. For some reason I cannot apply boundary conditions to the middle boundary of the rectangle for the NS app. It just says "not applicable." Any ideas why this might be the case? I would like to assign "moving wall" to this boundary, hopefully. I have v. 4.0. Thanks
2 Replies Last Post 2010/09/21 16:18 GMT-4
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Ah I see: When finalizing your geometry in the new geometry interface, the difference between "assembly" and "union" has implications for your interior boundaries (if you have them).
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Hi
yes you have "discovered" one of the differences of assemby and union: the creation of overlapping "common" boundaries that do not link by default via a "continuity" argument (but you can locally add this again by using identity pairs).
One thing though, if you do not need "all" your boundaries to be "assembled- dissociated", then you can perform a partial bolean "union" to group interiour "continuity" boundaries first, and just leave the few assembled ones for the final "finish - assembly"
In V3.5 you had this "feature" also possible by selecting interiour boundaries "on" to apply physics directly on the interiour boundaries.
There are still afew nice things in V3.5 not yet ready in current 4.0a, such as global pair generation so this is still to be done manually, but I have heard that it will soon be improved to have similar functionalities as under 3.5
--
Good luck
Ivar
yes you have "discovered" one of the differences of assemby and union: the creation of overlapping "common" boundaries that do not link by default via a "continuity" argument (but you can locally add this again by using identity pairs).
One thing though, if you do not need "all" your boundaries to be "assembled- dissociated", then you can perform a partial bolean "union" to group interiour "continuity" boundaries first, and just leave the few assembled ones for the final "finish - assembly"
In V3.5 you had this "feature" also possible by selecting interiour boundaries "on" to apply physics directly on the interiour boundaries.
There are still afew nice things in V3.5 not yet ready in current 4.0a, such as global pair generation so this is still to be done manually, but I have heard that it will soon be improved to have similar functionalities as under 3.5
--
Good luck
Ivar