Re: [Libmesh-users] ExodusII problems

[Derek G. <fri...@gm...>]

Ok fine.

I just committed a hack so that using Exodus with the examples works.... all it does is turn subdomain and boundary id's from 0 to 9999.  Ugly hack... but it does work.  I can't come up with something I really like better...

Derek

On Jan 17, 2010, at 1:29 PM, Przemyslaw Kaminski wrote:

> Hello,
> I'm trying to write the solution of example 11 into some file with a 
> format supported by Paraview. Unfortunately, it seems that VTK is not 
> well supported by libMesh. I've used exodusii then. But after including 
> the exodusii_io.h file, adding
> ExodusII_IO(mesh).write_equation_systems("out.g", equation_systems)
> and running the program, I get this:
> Mesh Information:
>  mesh_dimension()=2
>  spatial_dimension()=3
>  n_nodes()=961        
>    n_local_nodes()=961
>  n_elem()=225         
>    n_local_elem()=225 
>    n_active_elem()=225
>  n_subdomains()=1     
>  n_processors()=1     
>  processor_id()=0     
> 
> EquationSystems
>  n_systems()=1 
>   System "Stokes"
>    Type "LinearImplicit"
>    Variables="u" "v" "p" 
>    Finite Element Types="LAGRANGE" "LAGRANGE" "LAGRANGE" 
>    Approximation Orders="SECOND" "SECOND" "FIRST"        
>    n_dofs()=2178                                         
>    n_local_dofs()=2178                                   
>    n_constrained_dofs()=0                                
>    n_vectors()=1                                         
> 
> Num elem block: 1
> Error writing element block.
> [0] src/mesh/exodusII_io_helper.C, line 121, compiled Dec 12 2009 at 
> 22:34:13
> terminate called after throwing an instance of 'libMesh::LogicError'         
>  what():  Error in libMesh internal logic                                   
> [hp:09243] *** Process received signal ***                                   
> [hp:09243] Signal: Aborted (6)                                               
> [hp:09243] Signal code:  (-6)                                                
> [hp:09243] [ 0] /lib/libpthread.so.0(+0xee80) [0x7f6643319e80]               
> [hp:09243] [ 1] /lib/libc.so.6(gsignal+0x35) [0x7f6642fe6035]
> [hp:09243] [ 2] /lib/libc.so.6(abort+0x180) [0x7f6642fe7460]
> [hp:09243] [ 3] 
> /usr/lib/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x115) 
> [0x7f66456c7925]
> [hp:09243] [ 4] /usr/lib/libstdc++.so.6(+0xc6d56) [0x7f66456c5d56]
> [hp:09243] [ 5] /usr/lib/libstdc++.so.6(+0xc6d83) [0x7f66456c5d83]
> [hp:09243] [ 6] /usr/lib/libstdc++.so.6(+0xc6e7e) [0x7f66456c5e7e]
> [hp:09243] [ 7] /home/przemek/Build/libmesh-0.6.4/libmesh/lib/x86_64-
> unknown-linux-
> gnu_opt/libmesh.so(_ZN18ExodusII_IO_Helper9check_errEiSs+0x1b0) 
> [0x7f6647eb4800]
> [hp:09243] [ 8] /home/przemek/Build/libmesh-0.6.4/libmesh/lib/x86_64-
> unknown-linux-
> gnu_opt/libmesh.so(_ZN18ExodusII_IO_Helper14write_elementsERK8MeshBase+0x36b) 
> [0x7f6647eb988b]
> [hp:09243] [ 9] /home/przemek/Build/libmesh-0.6.4/libmesh/lib/x86_64-
> unknown-linux-
> gnu_opt/libmesh.so(_ZN11ExodusII_IO16write_nodal_dataERKSsRKSt6vectorIdSaIdEERKS2_ISsSaISsEE+0x43b) 
> [0x7f6647eb13ab]
> [hp:09243] [10] ./ex11-opt(main+0xe39) [0x484ea9]
> [hp:09243] [11] /lib/libc.so.6(__libc_start_main+0xfd) [0x7f6642fd2b6d]
> [hp:09243] [12] ./ex11-opt() [0x481d09]
> [hp:09243] *** End of error message ***
> 
> Does this mean that ExodusII is also not well supported?
> If so, what other format can I use, or maybe there exists a GMV <-> VTK 
> converter?
> Best regards,
> Przemek
> 
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Libmesh-users mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-users