Here's another "new" error when using the new contribs:
Exodus Library Error: [ex_put_block]
Error: failed to define number of nodes/entity for element block 507 in
file id 131072
[-41] netcdf constraint NC_MAX_DIMS exceeded
Error writing element block.
Stack frames: 14
0: 0 libmesh_dbg.0.dylib 0x000000010c0560e3
libMesh::print_trace(std::ostream&) + 39
1: 1 libmesh_dbg.0.dylib 0x000000010c3ea89b
libMesh::ExodusII_IO_Helper::check_err(int, std::string) + 103
2: 2 libmesh_dbg.0.dylib 0x000000010c3f1217
libMesh::ExodusII_IO_Helper::write_elements(libMesh::MeshBase const&) + 1165
3: 3 libmesh_dbg.0.dylib 0x000000010c3e62db
libMesh::ExodusII_IO::write_nodal_data(std::string const&,
std::vector<double, std::allocator<double> > const&,
std::vector<std::string, std::allocator<std::string> > const&) + 513
4: 4 libmesh_dbg.0.dylib 0x000000010c4a144c
libMesh::MeshOutput<libMesh::MeshBase>::write_equation_systems(std::string
const&, libMesh::EquationSystems const&, std::set<std::string,
std::less<std::string>, std::allocator<std::string> > const*) + 756
5: 5 libmesh_dbg.0.dylib 0x000000010c3e69a2
libMesh::ExodusII_IO::write_timestep(std::string const&,
libMesh::EquationSystems const&, int, double) + 76
6: 6 libmoose-dbg.0.dylib 0x000000010ad3043d
ExodusOutput::output(std::string const&, double) + 279
7: 7 libmoose-dbg.0.dylib 0x000000010ad34502 Output::output() + 86
8: 8 libmoose-dbg.0.dylib 0x000000010ab4bd8f FEProblem::output(bool) +
125
9: 9 libmoose-dbg.0.dylib 0x000000010ac62b14 Steady::execute() + 772
10: 10 libmoose-dbg.0.dylib 0x000000010abbf7cf
MooseApp::executeExecutioner() + 65
11: 11 libmoose-dbg.0.dylib 0x000000010abbff45 MooseApp::run() + 165
12: 12 pronghorn-dbg 0x00000001091f2385 main + 102
13: 13 libdyld.dylib 0x00007fff939fa7e1 start + 0
[0] src/mesh/exodusII_io_helper.C, line 235, compiled Feb 12 2013 at
10:09:24
terminate called after throwing an instance of 'libMesh::LogicError'
what(): Error in libMesh internal logic
[thearchitect:95296] *** Process received signal ***
[thearchitect:95296] Signal: Abort trap: 6 (6)
[thearchitect:95296] Signal code: (0)
[thearchitect:95296] *** End of error message ***
We have a number of tests that have started failing that use several
hundred subdomains. I haven't dived into this at all yet, but on the
surface it looks like we might need to call additional API functions or
something in our ExodusII_IO wrappers.
Just an FYI - I'll let you know when I get a chance to investigate.
Cody
On Tue, Feb 12, 2013 at 12:56 PM, Derek Gaston <fried...@gmail.com> wrote:
> Ok - we'll just stick to the old stuff for now until we can distribute
> HDF5.
>
> Derek
>
>
> On Tue, Feb 12, 2013 at 12:55 PM, Kirk, Benjamin (JSC-EG311) <
> benjamin.kir...@nasa.gov> wrote:
>
>> I think it is possible to use the new exodus even with the netcdf4
>> symbols missing, but I'm not sure yet what aspect of the new functionality
>> will be reduced.
>>
>> -Ben
>>
>>
>>
>> On Feb 12, 2013, at 1:28 PM, "Derek Gaston" <fried...@gmail.com> wrote:
>>
>> Didn't CC the list...
>>
>> ---------- Forwarded message ----------
>> From: Derek Gaston <fried...@gmail.com>
>> Date: Tue, Feb 12, 2013 at 12:27 PM
>> Subject: Re: [Libmesh-devel] Build Error
>> To: "Kirk, Benjamin (JSC-EG311)" <benjamin.kir...@nasa.gov>
>>
>>
>> On Tue, Feb 12, 2013 at 12:24 PM, Kirk, Benjamin (JSC-EG311) <
>> benjamin.kir...@nasa.gov> wrote:
>>
>>> This happens when HDF5 is not properly found, disabling netcdf4, but
>>> exodusII is still looking for that symbol
>>>
>>
>> I tried just --disable-hdf5 and that didn't do it either.
>>
>> Also - it's "--enable-netcdf=old" right? Not "with"? Or do both work?
>>
>> I can verify that turning everything (nemesis, netcdf, exodus) back to
>> old _does_ still work. But is kind of a bummer ;-)
>>
>> Going forward it looks like we (the MOOSE team) should distribute HDF5 to
>> our users....
>>
>> Derek
>>
>>
>> ------------------------------------------------------------------------------
>> Free Next-Gen Firewall Hardware Offer
>> Buy your Sophos next-gen firewall before the end March 2013
>> and get the hardware for free! Learn more.
>> http://p.sf.net/sfu/sophos-d2d-feb
>>
>> _______________________________________________
>> Libmesh-devel mailing list
>> Libmesh-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Libmesh-devel mailing list
> Libmesh-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>
>
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
