The Advanced Recording Format arf is an open standard for storing data from neuronal, acoustic, and behavioral experiments in a portable, high-performance, archival format. The goal is to enable labs to share data and tools, and to allow valuable data to be accessed and analyzed for many years in the future.
arf is built on the the HDF5 format, and all arf files are accessible through standard HDF5 tools, including interfaces to HDF5 written for other languages (e.g. MATLAB, Python, etc). arf comprises a set of specifications on how different kinds of data are stored. The organization of arf files is based around the concept of an entry, a collection of data channels associated with a particular point in time. An entry might contain one or more of the following:
raw extracellular neural signals recorded from a multichannel probe
spike times extracted from neural data
acoustic signals from a microphone
times when an animal interacted with a behavioral apparatus
the times when a real-time signal analyzer detected vocalization
Entries and datasets have metadata attributes describing how the data were collected. Datasets and entries retain these attributes when copied or moved between arf files, helping to prevent data from becoming orphaned and uninterpretable.
This repository contains:
The specification for arf (in specification.md). This is also hosted at https://meliza.org/spec:1/arf/.
A fast, type-safe C++ interface for reading and writing arf files
A python interface for reading and writing arf files
You don’t need the python or C++ libraries to read arf files; they are just standard HDF5 files that can be accessed with standard tools and libraries, like h5py (see below).
installation
ARF files require HDF5>=1.8 (http://www.hdfgroup.org/HDF5).
The python interface requires Python 3.11 or greater and h5py>=3.11. The last version of this package to support Python 2 was 2.5.1. The last version to support h5py 2 was 2.6.7.
The C++ interface needs only HDF5 and a C++11 compiler; it has no other dependencies. If writing multithreaded code, HDF5 needs to be compiled with --enable-threadsafe. The interface is header-only and does not need to be compiled. The recommended approach is to vendor a tagged version of the project and include the headers.
version information
The specification and implementations provided in this project use a form of semantic versioning (http://semver.org). Specifications receive a major and minor version number. Changes to minor version numbers must be backwards compatible (i.e., only added requirements). The current released version of the ARF specification is 2.2.
Implementation versions evolve independently from the specification. The current versions of the python and C++ packages will write ARF files using the 2.2 spec but can read any 2.x ARF file.
There was no public release of arf prior to 2.0.
access ARF files with HDF5 tools
The structure of an arf file can be explored using the h5ls tool. For example, to list entries:
$ h5ls file.arf
test_0001 Group
test_0002 Group
test_0003 Group
test_0004 Group
Each entry appears as a Group. To list the contents of an entry, use path notation:
$ h5ls file.arf/test_0001
pcm Dataset {609914}
This shows that the data in test_0001 is stored in a single node, pcm}, with 609914 data points. Typically each channel will have its own dataset.
The h5dump command can be used to output data in binary format. See the HDF5 documentation for details on how to structure the output. For example, to extract sampled data to a 16-bit little-endian file (i.e., PCM format):
h5dump -d /test_0001/pcm -b LE -o test_0001.pcm file.arf
contributing
ARF has been used by the Meliza lab for auditory systems neuroscience since 2013 and by Dan Meliza since he was a postdoc in 2006. We continue to maintain it, and we welcome comments and contributions from neuroscientists and behavioral biologists interested in using it. We’re particularly interested in use cases that don’t fit the current specification. Please post issues or contact Dan Meliza (dan at meliza.org) directly.
license
The reference implementations are released under the BSD 3-Clause License; see COPYING. The Specification itself (specification.md) is separately licensed under the GNU General Public License version 3 or later.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file arf-3.0.0.tar.gz.
File metadata
- Download URL: arf-3.0.0.tar.gz
- Upload date:
- Size: 14.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
36a021e70d998a1421a0cfc14f07519801bcaa6ad4a9846852c04a613607aaea
|
|
| MD5 |
b5b021ac0d0cbb654102eb92078b8721
|
|
| BLAKE2b-256 |
32f22467318a68b474d9f1bd7af857dcee67b5df4c04c014878d1ed9fd9cccf3
|
Provenance
The following attestation bundles were made for arf-3.0.0.tar.gz:
Publisher:
publish-to-pypi.yml on melizalab/arf
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
arf-3.0.0.tar.gz -
Subject digest:
36a021e70d998a1421a0cfc14f07519801bcaa6ad4a9846852c04a613607aaea - Sigstore transparency entry: 2386114923
- Sigstore integration time:
-
Permalink:
melizalab/arf@13836304322e203f918b5c349a03398ebcbf6455 -
Branch / Tag:
refs/tags/v3.0.0 - Owner: https://github.com/melizalab
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-to-pypi.yml@13836304322e203f918b5c349a03398ebcbf6455 -
Trigger Event:
push
-
Statement type:
File details
Details for the file arf-3.0.0-py3-none-any.whl.
File metadata
- Download URL: arf-3.0.0-py3-none-any.whl
- Upload date:
- Size: 17.1 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
e836c179125741816e88a105b4086f4143ebb28e0122447133151dfdfeaa5d2a
|
|
| MD5 |
e0daa5d7d9335d7a807c9f89cc365c96
|
|
| BLAKE2b-256 |
4cadf8b5ec9e581fe1ba21f131dbf338e0d201243ef1cad5c32eb79f12aa62e7
|
Provenance
The following attestation bundles were made for arf-3.0.0-py3-none-any.whl:
Publisher:
publish-to-pypi.yml on melizalab/arf
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
arf-3.0.0-py3-none-any.whl -
Subject digest:
e836c179125741816e88a105b4086f4143ebb28e0122447133151dfdfeaa5d2a - Sigstore transparency entry: 2386115784
- Sigstore integration time:
-
Permalink:
melizalab/arf@13836304322e203f918b5c349a03398ebcbf6455 -
Branch / Tag:
refs/tags/v3.0.0 - Owner: https://github.com/melizalab
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-to-pypi.yml@13836304322e203f918b5c349a03398ebcbf6455 -
Trigger Event:
push
-
Statement type: