Moved build_indexed_dataset from tests/C/query/common to tests/suite/programs and renamed it to build_standard_dataset, since it's generic and will be used in non-query-related tests later.
Made dataset listing/ID matching/etc. in build_standard_dataset more generic using a list of name-builderfunction pairs.
Renamed the datasets in build_standard_dataset to have more informative names and descriptions,
renamed the queries in tests/C/query/query-xmls, and added more messages to 19_query.sh.
Bugfix: ADIOS_VARCHUNKs returned by Transform layer should now have their from_steps/nsteps fields set properly
Renamed the selection intersection and data patching functions to 'global' variants, restricted them to all-global selection pairs, and added complementary 'local' variants that work on writeblocks and take additional context parameters. This rename did not extend into adios_transforms_read.c, since it is being heavily refactored.
Heavily refactored adios_transforms_read.c and related files to support writeblock selections as user selections AND as return datablock returns from transform plugins
Updated all transform plugins to return datablocks with writeblock selections where possible, instead of always bounding boxes, since this increases compatibility with the condition at adios_transforms_read.c:584
Bugfix: completed transformed-data read requests and VARCHUNK data buffers of returned de-transformed data are now properly freed cleaned up at the correct time during chunked reads. Previously, completed read reqests were freed immediately upon completion, invalidating the last varchunk returned to the user. Also, previous varchunk data buffers lent to the user were only freed upon a new varchunk arriving, leaving the last varchunk unfreed even if the first bug were fixed. Now, cleanup is done immediatly after any check_reads, including the final call that returns 0.
Added comments and removed extra newlines in some places
Now properly handling the data buffer from returned VARCHUNKs. Previously, we were keeping the actual ADIOS_VARCHUNK returned to the user, and freeing its buffer later. However, this is erroneous, as the user may (and is expected to) free the ADIOS_VARCHUNK. Instead, we now simply keep a pointer to the buffer itself.