maybe this helps

http://www.ansys.com/staticassets/ANSYS/Initial%20Content%20Entry/General%20Articles%20-%20Products/ICEM%20CFD%20Interfaces/cobalt.htm

praveen

On Fri, Nov 25, 2011 at 12:25 AM, Ted Kord <[email protected]> wrote:

> Thanks Praveen.
>
> How do I save in cobalt format? I'm using ICEM CFD 12.0 and there's no
> option to do this.
>
> TK
>
>
> On 24 November 2011 05:32, Praveen C <[email protected]> wrote:
>
>> I suspect that Nastran is saving the interior faces into the grid, and
>> gmsh is retaining them while converting. And deal.II maybe does not like
>> interior faces.
>>
>> If you can save mesh in cobalt format, I have a converter to gmsh format
>> here
>>
>> http://code.google.com/p/cfdlab/source/browse/trunk/3d/grid/cobalt2gmsh.c
>>
>> There is some scaling of coordinates done in the code which you can
>> delete.
>>
>> praveen
>>
>> On Wed, Nov 16, 2011 at 12:03 AM, Ted Kord <[email protected]> wrote:
>>
>>> Hi
>>>
>>> I wonder if anyone else has had this problem and could help with it.
>>>
>>> I used Ansys ICEM CFD to mesh a geometry and save it in Nastran .dat
>>> format. I then opened it in gmsh and converted it to .msh format. Trying to
>>> read the mesh in deal.II produces the following error:
>>>
>>> ----------------------------------------------------
>>> Exception on processing:
>>> --------------------------------------------------------
>>> An error occurred in line <2585> of file
>>> </home/tedkord/deal.II/source/grid/tria.cc> in function
>>>     static void
>>> dealii::internal::Triangulation::Implementation::create_triangulation(const
>>> std::vector<dealii::Point<dim, double>, std::allocator<dealii::Point<dim,
>>> double> > >&, const std::vector<dealii::CellData<3>,
>>> std::allocator<dealii::CellData<3> > >&, const dealii::SubCellData&,
>>> dealii::Triangulation<3, spacedim>&) [with int spacedim = 3]
>>> The violated condition was:
>>>     line->at_boundary()
>>> The name and call sequence of the exception was:
>>>     ExcInteriorLineCantBeBoundary()
>>> Additional Information:
>>> (none)
>>>
>>>
>>>
>>> This occurs for any nastran .dat mesh I convert in gmsh. My assumption's
>>> that if it can be read and converted in gmsh, then it should be readable in
>>> deal.II. Is this wrong?
>>>
>>> --
>>> Thanks
>>>
>>> Theodore K
>>>
>>>
>>>
>>> _______________________________________________
>>> dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
>>>
>>>
>>
>
>
> --
> Best regards,
>
> Theodore
>
>
>
_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii

Reply via email to