mirror of
https://github.com/Unidata/netcdf-c.git
synced 2024-11-27 07:30:33 +08:00
df3636b959
This PR started as an attempt to add unlimited dimensions to NCZarr. It did that, but this exposed significant problems with test interference. So this PR is mostly about fixing -- well mitigating anyway -- test interference. The problem of test interference is now documented in the document docs/internal.md. The solutions implemented here are also describe in that document. The solution is somewhat fragile but multiple cleanup mechanisms are provided. Note that this feature requires that the AWS command line utility must be installed. ## Unlimited Dimensions. The existing NCZarr extensions to Zarr are modified to support unlimited dimensions. NCzarr extends the Zarr meta-data for the ".zgroup" object to include netcdf-4 model extensions. This information is stored in ".zgroup" as dictionary named "_nczarr_group". Inside "_nczarr_group", there is a key named "dims" that stores information about netcdf-4 named dimensions. The value of "dims" is a dictionary whose keys are the named dimensions. The value associated with each dimension name has one of two forms Form 1 is a special case of form 2, and is kept for backward compatibility. Whenever a new file is written, it uses format 1 if possible, otherwise format 2. * Form 1: An integer representing the size of the dimension, which is used for simple named dimensions. * Form 2: A dictionary with the following keys and values" - "size" with an integer value representing the (current) size of the dimension. - "unlimited" with a value of either "1" or "0" to indicate if this dimension is an unlimited dimension. For Unlimited dimensions, the size is initially zero, and as variables extend the length of that dimension, the size value for the dimension increases. That dimension size is shared by all arrays referencing that dimension, so if one array extends an unlimited dimension, it is implicitly extended for all other arrays that reference that dimension. This is the standard semantics for unlimited dimensions. Adding unlimited dimensions required a number of other changes to the NCZarr code-base. These included the following. * Did a partial refactor of the slice handling code in zwalk.c to clean it up. * Added a number of tests for unlimited dimensions derived from the same test in nc_test4. * Added several NCZarr specific unlimited tests; more are needed. * Add test of endianness. ## Misc. Other Changes * Modify libdispatch/ncs3sdk_aws.cpp to optionally support use of the AWS Transfer Utility mechanism. This is controlled by the ```#define TRANSFER```` command in that file. It defaults to being disabled. * Parameterize both the standard Unidata S3 bucket (S3TESTBUCKET) and the netcdf-c test data prefix (S3TESTSUBTREE). * Fixed an obscure memory leak in ncdump. * Removed some obsolete unit testing code and test cases. * Uncovered a bug in the netcdf-c handling of big-endian floats and doubles. Have not fixed yet. See tst_h5_endians.c. * Renamed some nczarr_tests testcases to avoid name conflicts with nc_test4. * Modify the semantics of zmap\#ncsmap_write to only allow total rewrite of objects. * Modify the semantics of zodom to properly handle stride > 1. * Add a truncate operation to the libnczarr zmap code.
128 lines
3.4 KiB
Bash
Executable File
128 lines
3.4 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Define a function that attempts to locate a
|
|
# plugin with a given canonical name.
|
|
# Assumptions:
|
|
# 1. plugins is a top-level directory, possibly in "build"
|
|
# Inputs:
|
|
# $1 is the canonical name
|
|
# $2 is 1 if we are running under cmake
|
|
# $3 is 1 if we are running using Visual Studio, blank otherwise
|
|
# $4 is the build type; only used if $3 is 1
|
|
# Outputs:
|
|
# return code is 0 is success, 1 if failed
|
|
# Variable HDF5_PLUGIN_LIB is set to the library file name
|
|
# Variable HDF5_PLUGIN_DIR is set to the absolute path to the
|
|
# directory containing the plugin library file
|
|
# Local variables are prefixed with FP_
|
|
#
|
|
# Note: we assume that the use of the CMAKE_BUILD_TYPE
|
|
# is obviated by setting the LIBRARY_OUTPUT_DIRECTORY
|
|
# variables: see hdf5plugins/CMakeLists.txt
|
|
|
|
# Define location of execution
|
|
TOPSRCDIR='@abs_top_srcdir@'
|
|
TOPBUILDDIR='@abs_top_builddir@'
|
|
|
|
# Need info from test_common
|
|
if test "x$srcdir" = x ; then srcdir=`pwd`; fi
|
|
. ${TOPBUILDDIR}/test_common.sh
|
|
|
|
findpluginext() {
|
|
# Infer the expected plugin shared library extension
|
|
# Note: will fail if used before plugins is built
|
|
# Also assumes that misc filter is always built
|
|
# Approach is to use find to see what is in plugins directory.
|
|
TSO=`find ${TOPBUILDDIR}/plugins -name '*misc.so'`
|
|
TDY=`find ${TOPBUILDDIR}/plugins -name '*misc.dylib'`
|
|
TCYG=`find ${TOPBUILDDIR}/plugins -name 'cyg*misc.dll'`
|
|
TMING=`find ${TOPBUILDDIR}/plugins -name lib*misc.dll`
|
|
TDLL=`find ${TOPBUILDDIR}/plugins -name '*misc.dll'`
|
|
if test "x$TSO" != x ; then
|
|
FP_PLUGIN_EXT="so"
|
|
FP_PLUGIN_PRE="lib__nc"
|
|
elif test "x$TDY" != x ; then
|
|
FP_PLUGIN_EXT="dylib"
|
|
FP_PLUGIN_PRE="lib__nc"
|
|
elif test "x$TCYG" != x ; then
|
|
FP_PLUGIN_EXT="dll"
|
|
FP_PLUGIN_PRE="cyg__nc"
|
|
elif test "x$TMING" != x ; then
|
|
FP_PLUGIN_EXT="dll"
|
|
FP_PLUGIN_PRE="lib__nc"
|
|
elif test "x$TDLL" != x ; then
|
|
FP_PLUGIN_EXT="dll"
|
|
FP_PLUGIN_PRE="__nc"
|
|
else # unknown
|
|
echo "Cannot find plugin extension: please execute 'cd ../plugins; make check'"
|
|
exit 1
|
|
fi
|
|
}
|
|
|
|
findplugindir() {
|
|
FP_PLUGIN_DIR=
|
|
# Figure out the path to where the lib is stored
|
|
# This can probably be simplified
|
|
|
|
CURWD=`pwd`
|
|
cd ${TOPBUILDDIR}/plugins
|
|
FP_PLUGINS=`pwd`
|
|
cd ${CURWD}
|
|
|
|
# Case 1: Cmake with Visual Studio
|
|
if test "x$FP_ISCMAKE" != x -a "x${FP_ISMSVC}" != x ; then
|
|
# Case 1a: ignore the build type directory
|
|
if test -e "${FP_PLUGINS}/${FP_PLUGIN_LIB}" ; then
|
|
FP_PLUGIN_DIR="${FP_PLUGINS}"
|
|
fi
|
|
else # Case 2: automake
|
|
# Case 2a: look in .libs
|
|
if test -e "${FP_PLUGINS}/.libs" ; then
|
|
FP_PLUGIN_DIR="${FP_PLUGINS}/.libs"
|
|
else # Case 2: look in FP_PLUGINS directly
|
|
if test -e "${FP_PLUGINS}" ; then
|
|
FP_PLUGIN_DIR="${FP_PLUGINS}"
|
|
fi
|
|
fi
|
|
fi
|
|
|
|
# Verify
|
|
if test "x$FP_PLUGIN_DIR" = x ; then
|
|
echo "***Fail: Could not locate a usable $FP_PLUGIN_DIR"
|
|
return 1
|
|
fi
|
|
|
|
# Make local path
|
|
FP_PLUGIN_DIR=`${NCPATHCVT} -F $FP_PLUGIN_DIR`
|
|
HDF5_PLUGIN_DIR="$FP_PLUGIN_DIR"
|
|
if test "x$HDF5_PLUGIN_PATH" = x ; then
|
|
HDF5_PLUGIN_PATH="$HDF5_PLUGIN_DIR"
|
|
fi
|
|
}
|
|
|
|
findplugin() {
|
|
|
|
FP_NAME="$1"
|
|
|
|
FP_PLUGIN_LIB=
|
|
|
|
# Figure out the plugin file name
|
|
FP_PLUGIN_LIB="${FP_PLUGIN_PRE}${FP_NAME}.${FP_PLUGIN_EXT}"
|
|
|
|
# Verify
|
|
if ! test -f "$FP_PLUGIN_DIR/$FP_PLUGIN_LIB" ; then
|
|
echo "***Fail: Could not locate a usable $FP_PLUGIN_LIB"
|
|
return 1
|
|
fi
|
|
|
|
# Set the final output variables
|
|
HDF5_PLUGIN_LIB="$FP_PLUGIN_LIB"
|
|
HDF5_PLUGIN_DIR="$FP_PLUGIN_DIR"
|
|
return 0
|
|
}
|
|
|
|
# init
|
|
unset HDF5_PLUGIN_DIR
|
|
findpluginext
|
|
findplugindir
|