helppyFormex - Support: sr #108212, TriSurface.patchextension

 
 

sr #108212: TriSurface.patchextension

Submitted by:  gianluca de santis <gianlucadesi>
Submitted on:  Sat 22 Dec 2012 06:30:18 PM UTC  
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Privacy:  Public
Assigned to:  None Open/Closed:  Open
Operating System:  None

Add a New Comment (Rich Markup)
   

You are not logged in

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

 

Sat 22 Dec 2012 06:30:18 PM UTC, comment #1: 

This item has been reassigned from the project pyFormex task tracker to your tracker.

The original report is still available at task #12300

Following are the information included in the original report:

[field #0]                  Item ID: 12300
[field #1]                 Group ID: 10866
[field #2]              Open/Closed: Open
[field #3]                 Severity: 3 - Normal
[field #4]                  Privacy: Public
[field #9]                 Category: None
[field #10]             Submitted by: gianlucadesi
[field #11]              Assigned to: bverheg
[field #12]             Submitted on: Wed 31 Oct 2012 12:27:23 PM CET
[field #13]                  Summary: TriSurface.patchextension
[field #14]      Original Submission: The surface method patchextension is now deprecated and replaced with an example.

I think it is a very useful function to set up CFD analysis. Usually, a when a CFD domain (e.g. a vesse bifurcation) is obtained via CT/MRI segementation, it cannot yet be used for CFD analysis. The reason is that the user has impose a velocity filed on the inlet and sometimes also on some of the outlets. Because the inlet flow is usually known (measured) but the velocity field is not known (magnitude and orintation of the velocity vectors on every node.face of the inlet patch) the user often generate some flow extensions. Through this flow extension that velcotu filed can develop before reaching the region of interest. On the new-inlet the user applies simple velocity profiles (e.g.
      'flat' profile = same velocity on every inlet node/face with direction perpendicular to the inlet surface)
      'paraboloid' of Poiseuille: velocity magnitude depends on the radius and direction is always normal to surface.

     

In VTMK this function is called

http://www.vmtk.org/VmtkScripts/vmtkflowextensions/

The TriSurface.patchextension does the most important things:
1-extrude a patch (along normal or a user-defined direction)
2-allow to define the length of the extrusion based on average diameter of the patch (e.g. extrusion of 5*D)
3-allow the change the inlet border into a circular shape (useful in case of Poisuille paraboloid inlet velocity)

As nearly every CFD analysis required this function (previously done using VMTK) I feel that TriSurface.patchextension should stay in TriSurface and not be deprecated.

Comments are welcome

Gian
[field #16]               Item Group: None
[field #17]                   Status: In Progress
[field #18]        Component Version: None
[field #19]         Operating System: None
[field #20]          Reproducibility: None
[field #21]               Size (loc): None
[field #22]            Fixed Release: None
[field #23]          Planned Release: None
[field #24]                   Effort: 0.00
[field #28]                 Priority: 5 - Normal
[field #29]          Should Start On: Wed 31 Oct 2012 01:00:00 AM CET
[field #30]    Should be Finished on: Wed 31 Oct 2012 01:00:00 AM CET
[field #31]         Percent Complete: 0%
[field #33]                  Release: None
[field #58]     Custom Select Box #1: None
[field #59]     Custom Select Box #2: None
[field #60]     Custom Select Box #3: None
[field #61]     Custom Select Box #4: None
[field #62]     Custom Select Box #5: None
[field #63]     Custom Select Box #6: None
[field #64]     Custom Select Box #7: None
[field #65]     Custom Select Box #8: None
[field #66]     Custom Select Box #9: None
[field #67]    Custom Select Box #10: None

Benedict Verhegghe <bverheg>
Project Administrator
Sat 22 Dec 2012 06:30:18 PM UTC, original submission:  

The surface method patchextension is now deprecated and replaced with an example.

I think it is a very useful function to set up CFD analysis. Usually, a when a CFD domain (e.g. a vesse bifurcation) is obtained via CT/MRI segementation, it cannot yet be used for CFD analysis. The reason is that the user has impose a velocity filed on the inlet and sometimes also on some of the outlets. Because the inlet flow is usually known (measured) but the velocity field is not known (magnitude and orintation of the velocity vectors on every node.face of the inlet patch) the user often generate some flow extensions. Through this flow extension that velcotu filed can develop before reaching the region of interest. On the new-inlet the user applies simple velocity profiles (e.g.
      'flat' profile = same velocity on every inlet node/face with direction perpendicular to the inlet surface)
      'paraboloid' of Poiseuille: velocity magnitude depends on the radius and direction is always normal to surface.

     

In VTMK this function is called

http://www.vmtk.org/VmtkScripts/vmtkflowextensions/

The TriSurface.patchextension does the most important things:
1-extrude a patch (along normal or a user-defined direction)
2-allow to define the length of the extrusion based on average diameter of the patch (e.g. extrusion of 5*D)
3-allow the change the inlet border into a circular shape (useful in case of Poisuille paraboloid inlet velocity)

As nearly every CFD analysis required this function (previously done using VMTK) I feel that TriSurface.patchextension should stay in TriSurface and not be deprecated.

Comments are welcome

Gian

gianluca de santis <gianlucadesi>
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 (Submitted the item)
  •  

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

    Only logged-in users can vote.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2012-12-22 bverheg Reassign itempyFormex, task #12300 => pyFormex, sr #108212

    Back to the top


    Powered by Savane 3.5