[Katha]

Hello,

my question is regarding pointwise:

Is it possible, to somehow save the mesh settings (Delta s, growth, etc) and replace the database so that a slightly changed Version of the same geometry may be meshed with the exact same resolution?

e.g.: I have a mesh ready for a simple symmetric tee pipe with equally sized connections. Now lets assume I had a very similar geometry, again a tee, but this time the connections are, say, not orthogonal to each other.

What is the best way to quickly mesh the new database using the exact same mesh Settings as for the previous case.


FYI: I migrated from Centaur, where the mesh properties where assigned to Groups that in turn contained sets of connectors. In that way it was very simple to delete the old database, load a new one and assign it to the various groups, depending on which mesh settings they were supposed to inherit.


Thanks for any suggestions.

Regards, K

[lejonetfrannorden]

Hello Katha,

I am not a Pointwise expert but I think you could write a small script for that. IN order to do that you can use journaling. Under Script menu, click on start Begin Journaling. After you perform some operations you can use those in Journal to write the script you need.

Regards,
Lejonet

[Katha]

Hello Lejonet,

thx for your quick reply. I did consider scripting, but have not used it in pointwise yet.

Afaik, PW journaling references the connectors by their place in the list of all connectors, not by their name. Also, when I introduce the new database, the name conventions might not be the same as for the earlier one and the number of the connectors might change. The applications I am targeting are large databases, out of which the "majority" of the geometry stays the same. Only small sections change, and I want to find a way of making pointwise use the previous mesh settings, and lets me set new once for the changed database, while assigning the old settings to the unchanged parts of the database Hence, I imagine it will be difficult to use journaling.
Do let me know, if I am missing the obvious way of doing it.

Regards,
K

[Katha]

Hello Lejonet,

thx for your quick reply. I did consider journaling, but have not used it in pointwise yet.

Afaik, PW journaling references the connectors by their place in the list of all connectors, not by their name. Also, when I introduce the new database, the name conventions might not be the same as for the earlier one and the number of the connectors might change. The applications I am targeting are large databases, out of which the "majority" of the geometry stays the same. Only small sections change, and I want to find a way of making pointwise use the previous mesh settings, and lets me set new once for the changed database, while assigning the old settings to the unchanged parts of the database Hence, I imagine it will be difficult to use journaling.
Do let me know, if I am missing the obvious way of doing it.

Regards,
K

[lejonetfrannorden]

Hello Katha,

As I have pointed out this is the best I could have thought. I believe that you can still use it, however it would be computationally expensive due to changing and loading the majority of the same database. Sorry that I cannot help you further. Please post here if you come up with a solution!

Regards,
Lejonet

[Katha]

sure, thank you.

[dgarlisch]

This is possible but it can be fragile.

The database entities on which the grid entities are projected must have the same "topology" for the auto projection to work as expected.

By topology I mean same number DB ents with the same names NAMES. For example, if your grid is constrained to a six-face solid, you cannot bring in a seven-face solid.

If the topology is not the same, you will need to manually re-project (or script) the database doms and cons to the "similar" database ents.

For further help, please call Pointwise support.

See:
Save time by only remeshing the parts of your geometry model that change.

Saving Grid and Database Entities

[Katha]

ok, thank u david.