Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
H5D
and/orH5F
data for testing HDF5 data aggregation toolsin the new Python summary report
Targeted at darshan-hpc/darshan#663, these logs cover various cases that can be used to test some of the HDF5 aggregation.
For confirmation, here are some local prints of the relevant module data:
hdf5_file_opens_only.darshan
hdf5_diagonal_write_1_byte_dxt.darshan
hdf5_diagonal_write_bytes_range_dxt.darshan
hdf5_diagonal_write_half_flush_dxt.darshan
hdf5_diagonal_write_half_ranks_dxt.darshan
All of the DXT logs have a diagonal IO pattern similar to the logs from gh-22. The heatmap for
hdf5_diagonal_write_1_byte_dxt.darshan
(only "write") data:Not super important for HDF5 testing, but for
hdf5_diagonal_write_half_ranks_dxt.darshan
, you can actually observe a difference between ranks that wrote data out and ranks that didn't in the DXT data: