bugpyFormex - Bugs: bug #41144, Formex.toMesh()


bug #41144: Formex.toMesh()

Submitter:  gianluca de santis <gianlucadesi>
Submitted:  Wed 08 Jan 2014 09:16:12 AM UTC
Category:  Core Severity:  1 - Wish
Item Group:  Feature request Status:  Need Info
Privacy:  Public Assigned to:  bverheg
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Wed 08 Jan 2014 03:41:47 PM UTC, comment #1: 

I am not against it, as it would not compromise the current functionality (at least not in an important way), but I question its usefullness. An unfused Mesh is conceptually just the same as a Formex: it is not a single geometric domain but a collection of nelems unconnected domains, each consisting of a single element. Its coords would be exactly the same as the Formex' coords, but it would store an extra Connectivity, but that would be useless, as the elements are not connected at all. Most of the Mesh methods would fail to return a useful or expected result.

For a collection of nelems disconnected elements, the Formex class provides better functionality. So why not just use a Formex instead?
If there is some useful Mesh functionality for a nonfused Mesh, my first idea would be to see if it can easily be ported to a Formex. If not, then we should indeed add the option.

The situation is different if you have some subdomains which are fused, and you do not want to fuse the subdomains together. We currently have the List or fe.Model as a useful model here.
That is why mergeMeshes, mergeNodes have the fuse=False option.
The convert method has got the option because of some need when converting elements and having to trace back the converted parts to the original elements: the fuse is then usual done afterwards.

Finally, note that the current toMesh supports positional arguments (*args), so if we decide to add this option, we should check old code for situations where toMesh is used with such arguments (probably nowhere) and change these. And then remove the *args, so that in future only keyword parameters are allowed.

Benedict Verhegghe <bverheg>
Group administrator
Wed 08 Jan 2014 09:16:12 AM UTC, original submission:  

when converting a Formex to a Mesh you may need to avoid the fuse(), ie. you want that the element Connectivity of the Mesh is independent of the coordinates of the points of the original Formex. For example, when you are still creating the geometry made of multiple parts and occasionally some points have similar coordinates.

The minor change to
is in attachment.
NB: fuse = True/False is already used in some Mesh methods/functions:

I am not sure if this change is 'welcome'.
Would anybody benefit of this change?

gianluca de santis <gianlucadesi>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #30219:  formexToMesh.py added by gianlucadesi (700B - text/x-python)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by bverheg (Posted a comment)
  • -email is unavailable- added by gianlucadesi (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-01-08 bverheg CategoryNone Core
        Item GroupNone Feature request
        StatusNone Need Info
        Assigned toNone bverheg
    2014-01-08 gianlucadesi Attached File- Added formexToMesh.py, #30219

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code