bugpyFormex - Bugs: bug #43479, Mesh.toSurface shouldnt have the...

 
 

bug #43479: Mesh.toSurface shouldnt have the fuse parameter and to be passed to convert?

Submitted by:  francesco <francio>
Submitted on:  Mon 27 Oct 2014 01:08:08 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: Invalid
Privacy: PublicAssigned to: None
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Mon 27 Oct 2014 03:15:44 PM UTC, comment #6:

fine for me whatever solution you take, it was just not completely clear the purpose of the method due to the volume possibility.
closing the bug

francesco <francio>
Project Member
Mon 27 Oct 2014 03:09:09 PM UTC, comment #5:

Well, maybe it shouldn't, and we should let the user call getBorderMesh? I guess we added that so that the user would not have to call two functions. But I think that another name would be preferable, like Mesh.surface().

Benedict Verhegghe <bverheg>
Project Administrator
Mon 27 Oct 2014 03:04:28 PM UTC, comment #4:

ok now it is clearer, my confusion comes from the fact that toSurface does a getBorderMesh if a volume mesh is passed

francesco <francio>
Project Member
Mon 27 Oct 2014 02:51:54 PM UTC, comment #3:

You can not (should not) convert a volume to a surface.
The to... methods convert the internal representation, but keep the existing geometry.

Volume to Surface would require a method like getBorderMesh.

Benedict Verhegghe <bverheg>
Project Administrator
Mon 27 Oct 2014 02:33:28 PM UTC, comment #2:

You are right, this conversion does not give problems on quad4, and indeed can cause problems with a deafult fuse. Though toSurface also can work on volume meshes, so I think the parameter (default False) might be added, but the fuse can be done afterwards, so actually there is no advantage.
I think my problem comes from somewhere before the conversion

francesco <francio>
Project Member
Mon 27 Oct 2014 01:30:27 PM UTC, comment #1:

Mesh.toSurface: if the mesh is a tri3 it does nothing, if it is a quad4 it first convert to tri3. In the latter case, I think that the quad4 inherits the node list of the tri3 (no additional nodes are added) and only have a different element connectivity. Thus, I think that a fuse would be superfluous and may even introduce non-manifold entities.

gianluca de santis <gianlucadesi>
Project Member
Mon 27 Oct 2014 01:08:08 PM UTC, original submission:

can we add it, and actually should not it be the deafault for
toSurface to avoid manifolds?

francesco <francio>
Project Member

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 27 Oct 2014 03:15:44 PM UTCfrancioOpen/ClosedOpen=>Closed
    Mon 27 Oct 2014 02:51:54 PM UTCbverhegStatusNone=>Invalid

    Back to the top


    Powered by Savane 3.1-cleanup1