bugpyFormex - Bugs: bug #46105, getFreeEntities and related...

 
 

bug #46105: getFreeEntities and related methods should be moved from mesh.Mesh to connectivity

Submitter:  francesco <francio>
Submitted:  Fri 02 Oct 2015 04:11:58 PM UTC
 
Category:  Core Severity:  3 - Normal
Item Group:  Feature request Status:  None
Privacy:  Public Assigned to:  bverheg
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Mon 05 Oct 2015 10:07:30 AM UTC, comment #1: 

I would only move the getFreeEntities() to connectivity and put an example in the documentation.
The reason is that the user will rarely use the getFreeEntities() directly but he will regularly use the other methods (getBorder, getBorderElems, getBorderNodes) which are just calling the getFreeEntities().

gianluca de santis <gianlucadesi>
Project Member
Fri 02 Oct 2015 04:11:58 PM UTC, original submission:  

getFreeEntities ,  getBorder, getBorderNodes, getBorderElems and similar methods of mesh.Mesh are connectivity methods which do not use the coords table. We should move them in the connectivity.py

francesco <francio>
Project Member

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gianlucadesi (Posted a comment)
  • -email is unavailable- added by francio (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.

     

     

     

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.9