HSpy - HyperSpy’s HDF5 Specification#

This is HyperSpy’s default format and for data processed in HyperSpy, it is the only format that guarantees that no information will be lost in the writing process and that supports saving data of arbitrary dimensions. It is based on the HDF5 open standard. Parts of the specifications are documented in Metadata structure.

Added in version HyperSpy_v1.2: Enable saving HSpy files with the .hspy extension. Previously only the .hdf5 extension was recognised.

Changed in version HyperSpy_v1.3: The default extension for the HyperSpy HDF5 specification is now .hspy. The option to change the default is no longer present in preferences.

Only loading of HDF5 files following the HyperSpy specifications is supported by this plugin. Usually their extension is .hspy extension, but older versions of HyperSpy would save them with the .hdf5 extension. Both extensions are recognised by HyperSpy since version 1.2. However, HyperSpy versions older than 1.2 won’t recognise the .hspy extension. To work around the issue when using old HyperSpy installations simply change the extension manually to .hdf5 or directly save the file using this extension by explicitly adding it to the filename e.g.:

>>> import hyperspy.api as hs
>>> s = hs.signals.BaseSignal([0])
>>> s.save('test.hdf5')

Note

To read this format, the optional dependency h5py is required.

When saving to .hspy, all supported objects in the signal’s hyperspy.api.signals.BaseSignal.metadata are stored. This includes lists, tuples and signals. Please note that in order to increase saving efficiency and speed, if possible, the inner-most structures are converted to numpy arrays when saved. This procedure homogenizes any types of the objects inside, most notably casting numbers as strings if any other strings are present:

>>> # before saving:
>>> somelist
[1, 2.0, 'a name']
>>> # after saving:
['1', '2.0', 'a name']

The change of type is done using numpy “safe” rules, so no information is lost, as numbers are represented to full machine precision.

This feature is particularly useful when using exspy.signals.EDSSpectrum.get_lines_intensity():

>>> s = hs.datasets.example_signals.EDS_SEM_Spectrum()
>>> s.metadata.Sample.intensities = s.get_lines_intensity()
>>> s.save('EDS_spectrum.hspy')

>>> s_new = hs.load('EDS_spectrum.hspy')
>>> s_new.metadata.Sample.intensities
[<BaseSignal, title: X-ray line intensity of EDS SEM Signal1D: Al_Ka at 1.49 keV, dimensions: (|)>,
 <BaseSignal, title: X-ray line intensity of EDS SEM Signal1D: C_Ka at 0.28 keV, dimensions: (|)>,
 <BaseSignal, title: X-ray line intensity of EDS SEM Signal1D: Cu_La at 0.93 keV, dimensions: (|)>,
 <BaseSignal, title: X-ray line intensity of EDS SEM Signal1D: Mn_La at 0.63 keV, dimensions: (|)>,
 <BaseSignal, title: X-ray line intensity of EDS SEM Signal1D: Zr_La at 2.04 keV, dimensions: (|)>]

Chunking#

Added in version HyperSpy_v1.3.1: chunks keyword argument

The HyperSpy HDF5 format supports chunking the data into smaller pieces to make it possible to load only part of a dataset at a time. By default, the data is saved in chunks that are optimised to contain at least one full signal. It is possible to customise the chunk shape using the chunks keyword. For example, to save the data with (20, 20, 256) chunks instead of the default (7, 7, 2048) chunks for this signal:

>>> s = hs.signals.Signal1D(np.random.random((100, 100, 2048)))
>>> s.save("test_chunks", chunks=(20, 20, 256))

Note that currently it is not possible to pass different customised chunk shapes to all signals and arrays contained in a signal and its metadata. Therefore, the value of chunks provided on saving will be applied to all arrays contained in the signal.

By passing True to chunks the chunk shape is guessed using the guess_chunk function of h5py For large signal spaces, the autochunking usually leads to smaller chunks as guess_chunk does not impose the constrain of storing at least one signal per chunk. For example, for the signal in the example above passing chunks=True results in chunks of (7, 7, 256).

Choosing the correct chunk-size can significantly affect the speed of reading, writing and performance of many HyperSpy algorithms. See the HyperSpy chunking section for more information.

Note

Also see the HDF5 utility functions for inspecting HDF5 files.

Format description#

The root of the file must contain a group called Experiments. The Experiments group can contain any number of subgroups and each subgroup is an experiment or signal. Each subgroup must contain at least one dataset called data. The data is an array of arbitrary dimension. In addition, a number equal to the number of dimensions of the data dataset of empty groups called axis followed by a number must exist with the following attributes:

  • 'name'

  • 'offset'

  • 'scale'

  • 'units'

  • 'size'

  • 'index_in_array'

Alternatively to 'offset' and 'scale', the coordinate groups may contain an 'axis' vector attribute defining the axis points. The experiment group contains a number of attributes that will be directly assigned as class attributes of the hyperspy.api.signals.BaseSignal instance. In addition the experiment groups may contain 'original_metadata' and 'metadata'-subgroup that will be assigned to the same name attributes of the hyperspy.api.signals.BaseSignal instance as a hyperspy.misc.utils.DictionaryTreeBrowser. The Experiments group can contain attributes that may be common to all the experiments and that will be accessible as attributes of the Experiments instance.

Changelog#

v3.3#

  • Rename ragged_shapes dataset to _ragged_shapes_{key} where the key is the name of the corresponding ragged dataset.

v3.2#

  • Deprecated record_by attribute is removed

v3.1#

  • add read support for non-uniform DataAxis defined by 'axis' vector

  • move metadata.Signal.binned attribute to axes.is_binned parameter

v3.0#

  • add Camera and Stage node

  • move tilt_stage to Stage.tilt_alpha

v2.2#

  • store more metadata as string: date, time, notes, authors and doi

  • store quantity for intensity axis

v2.1#

  • Store the navigate attribute

  • record_by is stored only for backward compatibility but the axes navigate attribute takes precendence over record_by for files with version >= 2.1

v1.3#

  • Added support for lists, tuples and binary strings

API functions#

rsciio.hspy.file_reader(filename, lazy=False, **kwds)#

Read data from hdf5-files saved with the HyperSpy hdf5-format specification (.hspy).

Parameters:
filenamestr, pathlib.Path

Filename of the file to read or corresponding pathlib.Path.

lazybool, default=False

Whether to open the file lazily or not. The file will stay open until closed in compute() or closed manually. get_file_handle() can be used to access the file handler and close it manually.

**kwdsdict, optional

The keyword arguments are passed to h5py.File.

Returns:
list of dict

List of dictionaries containing the following fields:

  • ‘data’ – multidimensional numpy.ndarray or dask.array.Array

  • ‘axes’ – list of dictionaries describing the axes containing the fields ‘name’, ‘units’, ‘index_in_array’, and either ‘size’, ‘offset’, and ‘scale’ or a numpy array ‘axis’ containing the full axes vector

  • ‘metadata’ – dictionary containing the parsed metadata

  • ‘original_metadata’ – dictionary containing the full metadata tree from the input file

When the file contains several datasets, each dataset will be loaded as separate dictionary.

rsciio.hspy.file_writer(filename, signal, chunks=None, compression='gzip', close_file=True, write_dataset=True, show_progressbar=True, **kwds)#

Write data to HyperSpy’s hdf5-format (.hspy).

Parameters:
filenamestr, pathlib.Path

Filename of the file to write to or corresponding pathlib.Path.

signaldict

Dictionary containing the signal object. Should contain the following fields:

  • ‘data’ – multidimensional numpy array

  • ‘axes’ – list of dictionaries describing the axes containing the fields ‘name’, ‘units’, ‘index_in_array’, and either ‘size’, ‘offset’, and ‘scale’ or a numpy array ‘axis’ containing the full axes vector

  • ‘metadata’ – dictionary containing the metadata tree

chunkstuple of int or None, default=None

Define the chunking used for saving the dataset. If None, calculates chunks for the signal, with preferably at least one chunk per signal space.

compressionNone, ‘gzip’, ‘szip’, ‘lzf’, default=’gzip’

Compression can significantly increase the saving speed. If file size is not an issue, it can be disabled by setting compression=None. RosettaSciIO uses h5py for reading and writing HDF5 files and, therefore, it supports all compression filters supported by h5py. The default is 'gzip'. Also see notes below.

close_filebool, default=True

Close the file after writing. The file should not be closed if the data needs to be accessed lazily after saving.

write_datasetbool, default=True

If True, write the dataset, otherwise, don’t write it. Useful to overwrite attributes (for example axes_manager) only without having to write the whole dataset.

show_progressbarbool, default=True

Whether to show the progressbar or not.

**kwds

The keyword argument are passed to the h5py.Group.require_dataset() function.

Notes

It is possible to enable other compression filters such as blosc by installing e.g. hdf5plugin. Similarly, the availability of 'szip' depends on the HDF5 installation. If not available an error will be raised. Be aware that loading those files will require installing the package providing the compression filter and it may thus not be possible to load it on some platforms. Only compression=None and compression='gzip' are available on all platforms. For more details, see the h5py documentation.