colorado-boulder: resave to zea 0.1.7

#64

Resaves every colorado-boulder HDF5 file from zea 0.1.1 to zea 0.1.7 with zea data resave (zea 0.1.7).

Changed files: 62 total.

Folders changed:

  • colorado-boulder/Sub-dataset-1/: 10 files
  • colorado-boulder/Sub-dataset-2/: 10 files
  • colorado-boulder/Sub-dataset-3/: 42 files

What changes:

  • root attribute zea_version: 0.1.1 -> 0.1.7
  • new dataset tracks/track_0/transmit_only = False
  • field description attributes updated to the zea 0.1.7 wording (probe_center_frequency, focus_distances, tx_apodizations), and added to metadata/subject/{id,type}
  • storage: the old lzf compression is replaced by zea's default, so the files shrink from 22.7 GB to 14.0 GB and zea can read them concurrently

Raw RF data and acquisition data are untouched: every dataset in every resaved file, including raw_data, was compared element for element against the file on main and is identical. The metadata patch from #28 (metadata/subject/*, root us_machine) is carried over as is.

This makes the "zea v0.1.7" line in the updated data card (#52) true once both land.

Diff summary (one file per folder shown; all files in a folder have the same diff):

colorado-boulder/Sub-dataset-{1,2,3}/*.hdf5: differs
  ~ / (attrs): zea_version '0.1.1' -> '0.1.7'
  ~ metadata/subject/id (attrs): + description, unit
  ~ metadata/subject/type (attrs): + description, unit
  ~ probe/probe_center_frequency (attrs): description updated
  ~ tracks/track_0/scan/focus_distances (attrs): description updated
  ~ tracks/track_0/scan/tx_apodizations (attrs): description updated
  + tracks/track_0/transmit_only: False
NVIDIA org

Thanks @tristan-deep

wsimson changed pull request status to merged

Sign up or log in to comment