Find the handler corresponding to the given IO identifier.
Find the handler corresponding to the given IO identifier.
an IO identifier.
the corresponding IO handler, or a Failure if no handler was registered for the identifier.
Convenience method to load an object from an HDF5 group.
Convenience method to load an object from an HDF5 group. This method loads the IO metadata from the file, then uses the list of registered handlers to automatically find the corresponding IO handler, and finally uses that handler to load the object.
the HDF5 file containing the group.
the HDF5 group within the file to load the object from.
the object corresponding to the information in the HDF5 group.
Register an IO handler to make it available for loading and saving object instances.
Register an IO handler to make it available for loading and saving object instances.
the IO Handler to register.
Convenience method to store an object to an HDF5 group.
Convenience method to store an object to an HDF5 group. This method uses the list of registered handlers to automatically find the correct IO handler, then saves the object's metadata and uses the IO handler to save the object.
the object to save.
the HDF5 file containing the group.
the HDF5 group to save the object to.
Success or Failure
An object representing a collection of IO handlers providing load/save capabilities for a given object type. If there are multiple implementations for the given type (e.g., multiple image preprocessor implementations, multiple feature extractor implementations), they are distinguished (and uniquely identified) by their IO Identifiers (see HasIOIdentifier).
For every supported IO Identifier, a corresponding IOHandler must be registered using the
register()
method. The identifiers/handlers that come built into scalismo are automatically registered and available, but manual registration is required for user-defined handlers.the type of objects that can be loaded/saved
the type of the corresponding IO handlers