Hey Luca,
Thanks for your reply. Yes I understand we are dealing with an antique
here.. :)
We are not using FIDAP solver, but we have an in-house code that
specifically handle .FDNEUT mesh. Especially it reads the mesh based on the
entity groups as sorted out in FDNEUT.(e.g. inlet/outlet boundary). Of
course one possible long-term solution is to change our source code to
accommodate more popular mesh type nowadays. But we have already been
working with .FDNEUT for quite a number of cases. So we want to see if vmtk
can help us with that, without the use of GAMBIT (since it is also quite
old too).
And I am guessing to extend that, rewriting some part of
"vtkvmtkFDNEUTWriter" will do?
Thanks!
On 20 June 2013 16:35, Luca Antiga <luca.ant...@orobix.com> wrote:
> Hello Elaine,
> your message made me realize I haven't dealt with the FIDAP format
> in a long time! FIDAP was the first CFD solver I've ever used...
>
> Which brings me to the unfortunate consequence: the FDNEUT writer was
> written in the early days when there was no concept of CellEntityIds array
> in
> vmtkmeshwriter. So, while the writer produces a valid FDNEUT mesh, it
> doesn't
> take into account the entity information.
>
> It shouldn't be hard to extend the writer with the FDNEUT specs at hand.
>
> May I ask why you need the mesh in FDNEUT format? If it's not for using
> the FIDAP solver (which must have been abandoned for about ten years
> now) but for importing into, say, Gambit, then there might be other ways
> of getting there, through other formats that VTK supports.
>
> Best,
>
> Luca
>
>
>
>
> On Jun 18, 2013, at 10:37 PM, Elaine Tang wrote:
>
> > Hi,
> >
> > I am trying to create FDNEUT mesh using vmtk, and using .stl as input. I
> want to specify each inlet/outlet as separate entity in the FDNEUT. I first
> created an stl with open caps.Then I import the stl and mesh it to vtu.
> From vmtkmeshboundaryinspector, it seems that my vtu mesh contains the
> surface and each inlet/outlet cap as separate entities, which is great.
> However, when I try to output the mesh in FDNEUT, the CellEntityIfd cannot
> be stored in the FDNEUT mesh. And in the FDNEUT, the mesh is one entity as
> a whole. Any insight on this?
> >
> > Thanks!
> > --
> > Elaine Tang
> >
> > PhD Candidate
> > Cardiovascular Fluid Mechanics Laboratory
> > Chemical & Biomolecular Engineering
> > Georgia Institute of Technology
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> >
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> > vmtk-users mailing list
> > vmtk-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/vmtk-users
>
>
--
Elaine Tang
PhD Candidate
Cardiovascular Fluid Mechanics Laboratory
Chemical & Biomolecular Engineering
Georgia Institute of Technology
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
vmtk-users mailing list
vmtk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vmtk-users
