Streaming Data Types
FlatBuffers is the format chosen for the ISIS data streaming system, derived from the ESS messaging system.
Schema ids
| ID | File name | Description |
|---|---|---|
| f144 | f144_logdata.fbs |
Controls related log data, typically from EPICS or NICOS. Note: not to be used for array data |
| ev44 | ev44_events.fbs |
Multi-institution neutron event data for both single and multiple pulses |
| df12 | df12_det_spec_map.fbs |
Detector-spectrum map for Mantid |
| se00 | se00_data.fbs |
Used for storing arrays with optional timestamps, for example waveform data. Replaces senv. |
| ad00 | ad00_area_detector_array.fbs |
EPICS area detector array data |
| hs01 | hs01_event_histogram.fbs |
Event histogram stored in n dim array |
| ep01 | ep01_epics_connection.fbs |
Status or event of EPICS connection. Replaces ep00 |
| json | json_json.fbs |
Carries a JSON payload |
| pl72 | pl72_run_start.fbs |
File writing, run start message for file writer and Mantid |
| 6s4t | 6s4t_run_stop.fbs |
File writing, run stop message for file writer and Mantid |
| answ | answ_action_response.fbs |
Holds the result of a command to the filewriter |
| wrdn | wrdn_finished_writing.fbs |
Message from the filewriter when it is done writing a file |
| x5f2 | x5f2_status.fbs |
Status update and heartbeat message for any software |
| fc00 | fc00_forwarder_config.fbs |
Configuration update for Forwarder |
| al00 | al00_alarm.fbs |
Generic alarm schema for EPICS, NICOS, etc. |
| da00 | da00_dataarray.fbs |
Pseudo-scipp DataArray with time-dependent and constant Variables |
| un00 | un00_units.fbs |
Engineering units update |
| vc00 | vc00_veto_configuration.fbs |
Veto configuration update |
Adding new schemas
Add .fbs file to `schemas directory
Check ess-streaming-data-types first; attempt not to diverge without reason. If a new schema is really needed, then
add a new .fbs schema in the schemas directory.
Note: to generate code from .fbs schemas, you will need the flatc tool installed. It can be acquired from
https://github.com/google/flatbuffers/releases .
Adding Python bindings
Python bindings have low-level code (autogenerated by flatc) in the fbschemas directory, but also
manually-written convenience serializers and deserializers in the top-level of the python module.
When adding or modifying a schema:
- The low-level code must be generated by manually calling
flatc --python schemas\some_schema.fbsand adding the resulting generated code topython/src/streaming_data_types/fbschemas. - Manually-written serializers & deserializers will need to be updated, and added to the lists in
__init__.py.
Rust bindings
Rust bindings have low-level code in flatbuffers_generated, and a small high-level wrapper
to deserialize any message.
When adding or modifying a schema:
- The low-level code must be generated by calling
generate_rust_bindings.py - The wrapper (defined in
lib.rs) will need to be updated with the new schema.
1 maintainer
Metadata
1 maintainer
Release files for isis-streaming-data-types 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| isis_streaming_data_types-0.1.4.tar.gz | 60.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| isis_streaming_data_types-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.3 kB
Release files / isis_streaming_data_types-0.1.4.tar.gz
| Download URL | isis_streaming_data_types-0.1.4.tar.gz |
|---|---|
| Size | 60.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
851a334b3e1eefe62000a530d96d98750677b6d55e6e01f051516dfc8fa8a8d2
|
|
BLAKE2b-256 checksum How to use checksums |
3badba2b0fd995f11f69a8d73c46b3f9e0e44ca245a7d94ac4f4778e295a3d49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / isis_streaming_data_types-0.1.4-py3-none-any.whl
| Download URL | isis_streaming_data_types-0.1.4-py3-none-any.whl |
|---|---|
| Size | 74.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efd399ffe00e9d662fb8cea217417f321be7f637bec5f5770973aa1cb3d05251
|
|
BLAKE2b-256 checksum How to use checksums |
523395a0af4623e428feba474120a288418cf3f7876a0eacc390dc137f392fdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logSecurity for isis-streaming-data-types 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for isis_streaming_data_types-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
