netcdf-c/nczarr_test/ref_ut_proj.txt

Options: -ddim1=4 -v '4 v[dim1/2]' -s [0:4|0]
[r=0] ChunkRange{start=0 stop=2} Slice{0:4|0}
[0] Projection{id=1,chunkindex=0,first=0,last=1,limit=2,iopos=0,iocount=2,chunkslice=Slice{0:2|2},memslice=Slice{0:2|4}
[1] Projection{id=2,chunkindex=1,first=0,last=1,limit=4,iopos=2,iocount=2,chunkslice=Slice{0:2|2},memslice=Slice{2:4|4}
Options: -ddim1=6 -v '4 v[dim1/3]' -s [0:5|0]
[r=0] ChunkRange{start=0 stop=2} Slice{0:5|0}
[0] Projection{id=1,chunkindex=0,first=0,last=2,limit=3,iopos=0,iocount=3,chunkslice=Slice{0:3|3},memslice=Slice{0:3|6}
[1] Projection{id=2,chunkindex=1,first=0,last=1,limit=5,iopos=3,iocount=2,chunkslice=Slice{0:2|3},memslice=Slice{3:5|6}
Options: -ddim1=4 -ddim2=2 -v '4 v[dim1/2,dim2/2]' -s [2:3|0][0:2|0]
[r=0] ChunkRange{start=1 stop=2} Slice{2:3|0}
[0] Projection{id=1,chunkindex=1,first=0,last=0,limit=3,iopos=0,iocount=1,chunkslice=Slice{0:1|2},memslice=Slice{0:1|4}
[r=1] ChunkRange{start=0 stop=1} Slice{0:2|0}
[0] Projection{id=2,chunkindex=0,first=0,last=1,limit=2,iopos=0,iocount=2,chunkslice=Slice{0:2|2},memslice=Slice{0:2|2}
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			`Options: -ddim1=4 -v '4 v[dim1/2]' -s [0:4\|0]`
			`[r=0] ChunkRange{start=0 stop=2} Slice{0:4\|0}`
Fix some additional edges cases for mapping slices to chunks The code for mapping slices to chunks is wrong for some cases. Fix code and add additional chunking tests to cover edge cases. 2020-12-20 12:17:46 +08:00			`[0] Projection{id=1,chunkindex=0,first=0,last=1,limit=2,iopos=0,iocount=2,chunkslice=Slice{0:2\|2},memslice=Slice{0:2\|4}`
Additional Fixes to NCZarr Primary Fixes: * Add a whole variable optimization -- used in the rare case that nc_get/put_vara covers the whole of a variable and the variable has a single chunk. * Fix chunking error when stride causes whole chunks to be skipped. * Fix some memory leaks * Add test cases * Add one performance test to nczarr_test/. This uses the timer utils from unit_test: timer_utils.[ch]. * Move ncdumpchunks utility from ncdump to nczarr_test Misc. Other Changes: * Make check for aws libraries conditional on --enable-nczarr-s3 * Remove all but one bm tests from nczarr_test until they are working. * Remove another dependency on HDF5 from supposedly non-HDF5 specific code; specifically hdf5_log_hdf5. * Make the BAIL2 macro be hdf5 specific and replace elsewhere with an HDF5 independent equivalent. * Move hdf5cache.c to libsrc4/nc4cache.c because it is used by nczarr. * Modify unit_tests so that some of them are run even if using Windows. * Misc. small bug fixes and refactors and memory leaks. * Rename some conflicting tests for cmake. * Attempted to make nc_perf work with cmake and failed. 2020-12-17 11:48:02 +08:00			`[1] Projection{id=2,chunkindex=1,first=0,last=1,limit=4,iopos=2,iocount=2,chunkslice=Slice{0:2\|2},memslice=Slice{2:4\|4}`
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			`Options: -ddim1=6 -v '4 v[dim1/3]' -s [0:5\|0]`
			`[r=0] ChunkRange{start=0 stop=2} Slice{0:5\|0}`
Fix some additional edges cases for mapping slices to chunks The code for mapping slices to chunks is wrong for some cases. Fix code and add additional chunking tests to cover edge cases. 2020-12-20 12:17:46 +08:00			`[0] Projection{id=1,chunkindex=0,first=0,last=2,limit=3,iopos=0,iocount=3,chunkslice=Slice{0:3\|3},memslice=Slice{0:3\|6}`
			`[1] Projection{id=2,chunkindex=1,first=0,last=1,limit=5,iopos=3,iocount=2,chunkslice=Slice{0:2\|3},memslice=Slice{3:5\|6}`
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			`Options: -ddim1=4 -ddim2=2 -v '4 v[dim1/2,dim2/2]' -s [2:3\|0][0:2\|0]`
			`[r=0] ChunkRange{start=1 stop=2} Slice{2:3\|0}`
Fix some additional edges cases for mapping slices to chunks The code for mapping slices to chunks is wrong for some cases. Fix code and add additional chunking tests to cover edge cases. 2020-12-20 12:17:46 +08:00			`[0] Projection{id=1,chunkindex=1,first=0,last=0,limit=3,iopos=0,iocount=1,chunkslice=Slice{0:1\|2},memslice=Slice{0:1\|4}`
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			`[r=1] ChunkRange{start=0 stop=1} Slice{0:2\|0}`
Additional Fixes to NCZarr Primary Fixes: * Add a whole variable optimization -- used in the rare case that nc_get/put_vara covers the whole of a variable and the variable has a single chunk. * Fix chunking error when stride causes whole chunks to be skipped. * Fix some memory leaks * Add test cases * Add one performance test to nczarr_test/. This uses the timer utils from unit_test: timer_utils.[ch]. * Move ncdumpchunks utility from ncdump to nczarr_test Misc. Other Changes: * Make check for aws libraries conditional on --enable-nczarr-s3 * Remove all but one bm tests from nczarr_test until they are working. * Remove another dependency on HDF5 from supposedly non-HDF5 specific code; specifically hdf5_log_hdf5. * Make the BAIL2 macro be hdf5 specific and replace elsewhere with an HDF5 independent equivalent. * Move hdf5cache.c to libsrc4/nc4cache.c because it is used by nczarr. * Modify unit_tests so that some of them are run even if using Windows. * Misc. small bug fixes and refactors and memory leaks. * Rename some conflicting tests for cmake. * Attempted to make nc_perf work with cmake and failed. 2020-12-17 11:48:02 +08:00			`[0] Projection{id=2,chunkindex=0,first=0,last=1,limit=2,iopos=0,iocount=2,chunkslice=Slice{0:2\|2},memslice=Slice{0:2\|2}`