On Feb 12, 2013, at 2:49 PM, Cody Permann wrote:
>
> I need to increase some parameter bounds in netcdf - I'm doing that and will
> commit a fix if it still works.
>
> Excellent!
> Cody
It is in as of 4695b094f00c1076be21241050942414a2f22ac2
-Ben
--
On Tue, Feb 12, 2013 at 1:23 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
>
> On Feb 12, 2013, at 2:13 PM, Cody Permann wrote:
>
> > 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
>
On Feb 12, 2013, at 2:13 PM, Cody Permann wrote:
> 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
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.dyli
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 as
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"
mailto:fried...@gmail.com>> wrote:
Didn't CC the list...
-- Forwarded mess
