[Pointwise] why does joining takes so much time?
I try to join a number of (coons patch) surfaces which were created from curves. The joining of 128 such surfaces lasted for ~6000s(=1.5h) and the resulting file was ~260MB. Why does it last so long and why is the file so big? What other options do I have in Pointwise to join quite a few number (hundredish) of surfaces in a fair amount of time (max some minutes)?
Thanks in case someone can help or give ideas! Id appreciate it!
I wouldn't recommend joining surfaces, particularly since it's not necessary in Pointwise. There are couple of ways to approach this.
First, if you want to reduce the number of "meshable" surfaces, I suggest you use the solid modeling cabaility. Solid modeling allows you to "join" surfaces not a physical sense - which is very computationally expensive as you've found out - but in a topological sense. The way I think of solid modeling is that it's creating a "glue" that describes how adjacent surfaces should be connected to each. I won't describe how to use solid modeling here, you'll want to refer to tutorial #3 of the tutorial workbook (found in Help > About). Since you have a lot of surfaces you want to "join", pay particular attention to the section on quilting.
Check out this video for a quick overview of solid modeling:
There other approach is to not join or use solid modeling, instead leaving the surfaces as is, create surface meshes on all the surfaces and join the surface meshes. This technique is called fault-tolerant meshing.
Check out this video for a quick overview of fault-tolerant:
Let me know if this is what you're after.
firstly thanks for the quick reply!
Secondly, I admit I should have explained, but I am about to create a special surface made out of several bits. Thus, I am not dealing with a dirty geometry with tiny little unwanted surfaces, but all of my surface elements are needed. Those surface elements will create the whole surface.
Still, your recommendations are good although not breaking the ice:
The 1st way: (I tried this)
I assemble the model, but then I have lots of quilts (same number as the number of surface elements). But then I will have lots of connectors when I create connectors on database entities. So then I have to delete the unwanted connectors and join lots of others...
The 2nd way (was about to continue this way):
I leave surfaces as is the create the connectors on them, then delete and join as before (only I dont have many useless quilts and a model).
Lastly, back to the beginning:
Could you explain me why is it so computationally expensive to join the surfaces?
s is not there
By the way, I made a grammatical mistake in the topic name...
Remember, when you mesh a model, Pointwise will create one domain for each quilt. So reducing the number of quilts will reduce the total number of entities.
Now that I think about, this is precisely how and why CAD packages construct "solids" from a collection of surfaces. It's much easer (and likely more robust) to create a complex object from simple fundamental entities and tie them together with topological "glue" than one large entity. Our solid modeling capability, uses the same principles that a full feature CAD system does for assembling solids. BTW, there is no requirement that a solid model be closed - it's pefectly valid for them to be open.
Phew ... I digress.
Getting back to your original inquiry, let me know if I'm still pointing you in the right direction or I'm getting further off base.
okey, due to your suggestions I think I found the best way finally:
1. create assemble models on the series of surfaces
2. join the quilts with create-assemble quilts (just found this out today, before I would have tried edit-join (as it greyed out)
3. Create connectors on the joined surfacepatch-quilt, then I just join the connectors on two sides of the assembled surface (lets say along u direction of the surface).
Nice, thanks a lot again, you pointed me to the good direction!
About the analytical join: I can grasp it a bit, thanks for the info.
Still, it would be nice to make a faster analytical reapproximator. I think Pointwise tries to reapproximate the surface elements with the given tolerance but to reach this prescribed level of tolerance it has to use lots of terms in the equation of the NURB describing the joined surface. This might be the reason for huge .pw file size and longlasting effort...but not sure though...
Yet another question:
Based on what Pointwise decides on whether a domain can be created on existing databases? I have assembled my surfaces to a model and I can't create domain on it (it is a squre-like surface), whereas Pointwise allows me to do that in case of the prepared geometry avalable for download from here. What should I do with model databases in order to be avalable for creating domains on them?
Thnaks in advance!
Negative volumes Pointwise-Fluent
I have a great trouble since some 2 weeks. I have to perform mesh in Pointwise, but.....there is a problem.
In Pointwise when I check the grid for negative volumes, I do not have any message for their existence. After reading in Fluent-the programm gives me message that there are negative volumes and left-handed elements.
Please, help me to solve that problem. I needed to have solution before Christmas, but now.....
Many thanks in advance
Pointwise- gaps among the database
let me ask another thing - I have second file with gaps between 2 adjacent databases
I tried to glue/merge the databases- quilts, models.....but there is a message that models are merged and then I see them, after significant zoom in, that again have gaps in Pointwise.
Thank you I advance for your kind help
Mar777, I strongly suggest you make NEW posts for your two questions. New posts get a lot more attention.
It is highly unlikely you will get a quick answer when adding a new question to the end of a thread that is over 3 years old.
|All times are GMT -4. The time now is 05:41.|