| Crates.io | frib_datasource |
| lib.rs | frib_datasource |
| version | 0.1.4 |
| created_at | 2026-01-16 16:11:59.572336+00 |
| updated_at | 2026-01-22 15:17:13.397083+00 |
| description | Data sources for FRIB ringitem data |
| homepage | http://docs.nscl.msu.edu/daq |
| repository | https://github.com/FRIBDAQ/rust_frib_datasource.git |
| max_upload_size | |
| id | 2048849 |
| size | 41,382 |
This repository provides a rust module that support source independent access of FRIB/NSCLDAQ ring item data. Ring items can come from live (ring buffers) or they can come from offline (file) data.
Data sources are specified by URIs of the form:
sourcetype://source-specification
Valid sourcetypes are:
tcp data comes from a (possibly) remote ring item.file data comes from a file.These have two components. The first is the host on which the ring item is located. The second is the name of the ringbuffer in that host. For example:
tcp://spdaq08.frib.msu.edu/aring
Fetches is a data source from the ring named aring in the host
spdaq08.frib.msu.edu
Note that to use online ring buffers, the FRIB/NSCLDAQ port manager and ringmaster must be running in all involved systems. In the example URI above, the ringmaster and port manager must be running in both the requesting host and spdaq08.frib.msu.edu
This is just the path to the file that contains the data. For example:
file://run-0001-01.evt
Specifies run-0001-01.evt in the current working directory.
Note that:
~ expansion is not supported
Environment variable name substitution is not supported.
The special value - represents stdin. This is useful to allow
a program to operate as a pipeline element.