n5 0.6.1

Rust implementation of the N5 tensor file system format
docs.rs failed to build n5-0.6.1
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: n5-0.7.6

N5 Build Status Coverage

A (mostly pure) rust implementation of the N5 "Not HDF5" n-dimensional tensor file system storage format created by the Saalfeld lab at Janelia Research Campus.

Compatible with Java N5 Version 2.1.3.

Differences from Java N5

  • Dataset paths are relative. The root path in a dataset is "", not "/".
  • Dataset paths are more strict. Calling methods with paths outside the dataset, e.g., "..", will return a Result::Err.

Minimum supported Rust version (MSRV)

Stable 1.39

Quick start

[dependencies]
n5 = "0.6"
use n5::prelude::*;
use n5::smallvec::smallvec;

fn n5_roundtrip(root_path: &str) -> std::io::Result<()> {
    let n = N5Filesystem::open_or_create(root_path)?;

    let block_size = smallvec![44, 33, 22];
    let data_attrs = DatasetAttributes::new(
        smallvec![100, 200, 300],
        block_size.clone(),
        DataType::INT16,
        CompressionType::default(),
    );
    let block_data: Vec<i16> = vec![0i16; data_attrs.get_block_num_elements()];

    let block_in = VecDataBlock::new(
        block_size,
        smallvec![0, 0, 0],
        block_data.clone());

    let path_name = "test/dataset/group";

    n.create_dataset(path_name, &data_attrs)?;
    n.write_block(path_name, &data_attrs, &block_in)?;

    let block_out = n.read_block::<i16>(path_name, &data_attrs, smallvec![0, 0, 0])?
        .expect("Block is empty");
    assert_eq!(block_out.get_data(), &block_data);

    Ok(())
}

fn main() {
    n5_roundtrip("tmp.n5").expect("N5 roundtrip failed!");
}

Status

This library is compatible with all N5 datasets the authors have encountered and is used in production services. However, some aspects of the library are still unergonomic and interfaces may still undergo rapid breaking changes.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.