2014-08-30 04:51:14 +08:00
|
|
|
# NetCDF C Configuration Summary
|
2014-08-25 06:29:44 +08:00
|
|
|
==============================
|
2014-05-31 03:36:35 +08:00
|
|
|
|
2014-08-30 04:51:14 +08:00
|
|
|
# General
|
2014-05-31 03:36:35 +08:00
|
|
|
-------
|
2014-05-31 05:30:58 +08:00
|
|
|
NetCDF Version: @PACKAGE_VERSION@
|
2019-11-20 06:14:26 +08:00
|
|
|
Dispatch Version: @NC_DISPATCH_VERSION@
|
2014-05-31 05:30:58 +08:00
|
|
|
Configured On: @CONFIG_DATE@
|
|
|
|
|
Host System: @host_cpu@-@host_vendor@-@host_os@
|
|
|
|
|
Build Directory: @abs_top_builddir@
|
2019-11-20 06:14:26 +08:00
|
|
|
Install Prefix: @prefix@
|
2014-05-31 03:36:35 +08:00
|
|
|
|
2014-08-30 04:51:14 +08:00
|
|
|
# Compiling Options
|
2014-05-31 03:36:35 +08:00
|
|
|
-----------------
|
2014-08-25 06:29:44 +08:00
|
|
|
C Compiler: @CC_VERSION@
|
|
|
|
|
CFLAGS: @CFLAGS@
|
|
|
|
|
CPPFLAGS: @CPPFLAGS@
|
|
|
|
|
LDFLAGS: @LDFLAGS@
|
|
|
|
|
AM_CFLAGS: @AM_CFLAGS@
|
|
|
|
|
AM_CPPFLAGS: @AM_CPPFLAGS@
|
|
|
|
|
AM_LDFLAGS: @AM_LDFLAGS@
|
|
|
|
|
Shared Library: @enable_shared@
|
|
|
|
|
Static Library: @enable_static@
|
|
|
|
|
Extra libraries: @LIBS@
|
2021-11-03 05:35:04 +08:00
|
|
|
XML Parser: @XMLPARSER@
|
2014-05-31 03:36:35 +08:00
|
|
|
|
2014-08-30 04:51:14 +08:00
|
|
|
# Features
|
2014-08-25 06:29:44 +08:00
|
|
|
--------
|
|
|
|
|
NetCDF-2 API: @HAS_NC2@
|
|
|
|
|
HDF4 Support: @HAS_HDF4@
|
2018-11-29 06:50:38 +08:00
|
|
|
HDF5 Support: @HAS_HDF5@
|
2015-11-18 07:31:29 +08:00
|
|
|
NetCDF-4 API: @HAS_NC4@
|
2015-08-16 06:26:35 +08:00
|
|
|
NC-4 Parallel Support: @HAS_PARALLEL4@
|
2018-09-18 00:47:40 +08:00
|
|
|
PnetCDF Support: @HAS_PNETCDF@
|
Upgrade the nczarr code to match Zarr V2
Re: https://github.com/zarr-developers/zarr-python/pull/716
The Zarr version 2 spec has been extended to include the ability
to choose the dimension separator in chunk name keys. The legal
separators has been extended from {'.'} to {'.' '/'}. So now it
is possible to use a key like "0/1/2/0" for chunk names.
This PR implements this for NCZarr. The V2 spec now says that
this separator can be set on a per-variable basis. For now, I
have chosen to allow this be set only globally by adding a key
named "ZARR.DIMENSION_SEPARATOR=<char>" in the
.daprc/.dodsrc/ncrc file. Currently, the only legal separator
characters are '.' (the default) and '/'. On writing, this key
will only be written if its value is different than the default.
This change caused problems because supporting a separator of '/'
is difficult to parse when keys/paths use '/' as the path separator.
A test case was added for this.
Additionally, make nczarr be enabled default by default. This required
some additional changes so that if zip and/or AWS S3 sdk are unavailable,
then they are disabled for NCZarr.
In addition the following unrelated changes were made.
1. Tested that pure-zarr mode could read an nczarr formatted store.
1. The .rc file handling now merges all known .rc files (.ncrc,.daprc, and .dodsrc) in that order and using those in HOME first, then in current directory. For duplicate entries, the later ones override the earlier ones. This change is to remove some of the conflicts inherent in the current .rc file load process. A set of test cases was also added.
1. Re-order tests in configure.ac and CMakeLists.txt so that if libcurl
is not found then the other options that depend upon it properly
are disabled.
1. I decided that xarray support should be enabled by default for pure
zarr. In order to allow disabling, I added a new mode flag "noxarray".
1. Certain test in nczarr_test depend on use of .dodsrc. In order for these
to work when testing in parallel, some inter-test dependencies needed to
be added.
1. Improved authorization testing to use changes in thredds.ucar.edu
2021-04-25 09:48:15 +08:00
|
|
|
DAP2 Support: @HAS_DAP2@
|
2017-03-09 08:01:10 +08:00
|
|
|
DAP4 Support: @HAS_DAP4@
|
2019-02-25 07:54:13 +08:00
|
|
|
Byte-Range Support: @HAS_BYTERANGE@
|
2014-08-25 06:29:44 +08:00
|
|
|
Diskless Support: @HAS_DISKLESS@
|
|
|
|
|
MMap Support: @HAS_MMAP@
|
|
|
|
|
JNA Support: @HAS_JNA@
|
2017-09-14 05:25:40 +08:00
|
|
|
CDF5 Support: @HAS_CDF5@
|
2018-09-05 01:27:47 +08:00
|
|
|
ERANGE Fill Support: @HAS_ERANGE_FILL@
|
2020-01-25 07:36:29 +08:00
|
|
|
Relaxed Boundary Check: @RELAX_COORD_BOUND@
|
2020-01-07 07:41:08 +08:00
|
|
|
SZIP Support: @HAS_SZLIB@
|
2020-02-03 04:55:58 +08:00
|
|
|
SZIP Write Support: @HAS_SZLIB_WRITE@
|
2020-01-17 00:19:24 +08:00
|
|
|
Parallel Filters: @HAS_PAR_FILTERS@
|
This PR adds EXPERIMENTAL support for accessing data in the
cloud using a variant of the Zarr protocol and storage
format. This enhancement is generically referred to as "NCZarr".
The data model supported by NCZarr is netcdf-4 minus the user-defined
types and the String type. In this sense it is similar to the CDF-5
data model.
More detailed information about enabling and using NCZarr is
described in the document NUG/nczarr.md and in a
[Unidata Developer's blog entry](https://www.unidata.ucar.edu/blogs/developer/en/entry/overview-of-zarr-support-in).
WARNING: this code has had limited testing, so do use this version
for production work. Also, performance improvements are ongoing.
Note especially the following platform matrix of successful tests:
Platform | Build System | S3 support
------------------------------------
Linux+gcc | Automake | yes
Linux+gcc | CMake | yes
Visual Studio | CMake | no
Additionally, and as a consequence of the addition of NCZarr,
major changes have been made to the Filter API. NOTE: NCZarr
does not yet support filters, but these changes are enablers for
that support in the future. Note that it is possible
(probable?) that there will be some accidental reversions if the
changes here did not correctly mimic the existing filter testing.
In any case, previously filter ids and parameters were of type
unsigned int. In order to support the more general zarr filter
model, this was all converted to char*. The old HDF5-specific,
unsigned int operations are still supported but they are
wrappers around the new, char* based nc_filterx_XXX functions.
This entailed at least the following changes:
1. Added the files libdispatch/dfilterx.c and include/ncfilter.h
2. Some filterx utilities have been moved to libdispatch/daux.c
3. A new entry, "filter_actions" was added to the NCDispatch table
and the version bumped.
4. An overly complex set of structs was created to support funnelling
all of the filterx operations thru a single dispatch
"filter_actions" entry.
5. Move common code to from libhdf5 to libsrc4 so that it is accessible
to nczarr.
Changes directly related to Zarr:
1. Modified CMakeList.txt and configure.ac to support both C and C++
-- this is in support of S3 support via the awd-sdk libraries.
2. Define a size64_t type to support nczarr.
3. More reworking of libdispatch/dinfermodel.c to
support zarr and to regularize the structure of the fragments
section of a URL.
Changes not directly related to Zarr:
1. Make client-side filter registration be conditional, with default off.
2. Hack include/nc4internal.h to make some flags added by Ed be unique:
e.g. NC_CREAT, NC_INDEF, etc.
3. cleanup include/nchttp.h and libdispatch/dhttp.c.
4. Misc. changes to support compiling under Visual Studio including:
* Better testing under windows for dirent.h and opendir and closedir.
5. Misc. changes to the oc2 code to support various libcurl CURLOPT flags
and to centralize error reporting.
6. By default, suppress the vlen tests that have unfixed memory leaks; add option to enable them.
7. Make part of the nc_test/test_byterange.sh test be contingent on remotetest.unidata.ucar.edu being accessible.
Changes Left TO-DO:
1. fix provenance code, it is too HDF5 specific.
2020-06-29 08:02:47 +08:00
|
|
|
NCZarr Support: @HAS_NCZARR@
|
2020-09-28 02:43:46 +08:00
|
|
|
Multi-Filter Support: @HAS_MULTIFILTERS@
|
2021-08-24 14:45:38 +08:00
|
|
|
Quantization: @HAS_QUANTIZE@
|
2021-08-24 14:19:41 +08:00
|
|
|
Logging: @HAS_LOGGING@
|
