Re: [Libmesh-users] Gradient of C1 error

[Ataollah M. <am...@ti...>]

Ok done. You are right, when I write the output in Nemesis format it messes up the gradient. You can get my tweaked adaptivity_ex4 from: http://cl.ly/02131w2o2715 . So does this mean that this is a VisIt bug?!

PS: I had to make it so it reads a mesh file otherwise Nemesis_IO wouldn't work and I would get: this in trace:

0: libMesh::print_trace(std::ostream&)
1: libMesh::libmesh_terminate_handler()
2: /usr/lib64/libstdc++.so.6() [0x37a12bcc06]
3: /usr/lib64/libstdc++.so.6() [0x37a12bcc33]
4: /usr/lib64/libstdc++.so.6() [0x37a12bcd2e]
5: libMesh::Nemesis_IO_Helper::write_sidesets(libMesh::MeshBase const&)
6: libMesh::Nemesis_IO::write_nodal_data(std::string const&, std::vector<double, std::allocator<double> > const&, std::vector<std::string, std::allocator<std::string> > const&)
7: ./adap4-opt() [0x410d47]
8: ./adap4-opt() [0x412daa]
9: __libc_start_main
10: ./adap4-opt() [0x40e779]


 

Ata

On Dec 4, 2012, at 3:22 PM, Ataollah Mesgarnejad <am...@ti...> wrote:

> 
> On Dec 4, 2012, at 3:14 PM, Roy Stogner <roy...@ic...> wrote:
> 
>> 
>> On Tue, 4 Dec 2012, Ataollah Mesgarnejad wrote:
>> 
>>>> If it is a problem in library code... I don't suppose there's any
>>>> chance you could reproduce it with a tweaked adaptivity_ex4 ?
>>> 
>>> What if I tweak it to swap the solution with |gradu-exact_gradu|  so we can see the error on mesh partition ?
>> 
>> I just meant weaking it to use CLOUGH (config file change) and to use
>> whatever output file format you're seeing your own problem with (if
>> that's not Exodus, then running in parallel, then checking the
>> solution in VisIt like you'd do for your own code.  That ought to be
>> sufficient to demonstrate any I/O or core problem in the library.
> 
> OK. That's easy. I will get back to you as soon as I have something.
> 
> Ata
> 
>> ---
>> Roy
>