Your message dated Sat, 13 Aug 2016 17:58:25 +0200
with message-id <[email protected]>
and subject line Re: Bug#749859: netcdf: Please increase size of netcdf models
for exodus
has caused the Debian Bug report #749859,
regarding netcdf: Please increase size of netcdf models for exodus
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
749859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749859
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: netcdf
Version: 4.2.1+
Severity: normal
I maintain the ExodusII package, which has in its README:
The exodus library uses the netcdf library for low-level data
storage.
Exodus requires NetCDF version 4.2.1.1 or later.
The netcdf library must be modified slightly in order to handle the
exodus datamodel. The specific changes are:
1. include/netcdf.h -- Modify the following defines:
#define NC_MAX_DIMS 65536 /* max dimensions per file */
#define NC_MAX_VARS 524288 /* max variables per file */
#define NC_MAX_VAR_DIMS 8 /* max per variable dimensions */
If these changes are not made, the exodus library will still function
for "normal" size models, but it will fail for "large" models. The
error message from exodus/netcdf should be somewhat clear when this
happens...
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On 12/24/15 19:35, Sebastiaan Couwenberg wrote:
The upstream issue in the GitHub tracker has been closed. While that
discussion isn't very conclusive, the related issues show that
upstream doesn't want to change these values either, and recommends to
build a exodus-netcdf library specifically for exodusII. I suggest you
investigate the feasibility of the approach suggested by Ward in:
https://github.com/Unidata/netcdf-c/pull/166#issuecomment-163329126
Because I'm as uncomfortable as netcdf upstream about changing the
values in netcdf itself, having exodusII build its own tweaked netcdf
library is better option to resolve the issue there. Perhaps you can
help tweak the script as part of your packaging effort and contribute
that for the benefit of the wider exodusII community.
Closing this issue per the above.
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
