Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

larpix-daq

Documentation Status

LArPix DAQ is the data acquisition system for LArPix. It handles the data flow between the "data boards" and offline storage and includes data monitoring and operator control functionality built on the xylem DAQ framework.

LArPix DAQ consists of a set of scripts which are responsible for individual parts of the DAQ system's functionality, as well as an operator interface API which can be run in an interactive python session or used as a basis for a more sophisticated interactive program. The scripts can be run from the same or from different computers, as long as the IP addresses of the various computers are known.

System states

There are three states the system can be in: READY, RUN, and STOP. The state is controlled through the Operator object using the methods prepare_run (transition to READY), begin_run (transition to START), and end_run (transition to STOP).

  • STOP: Default state on startup. All components are not expecting data.
  • READY: Components should prepare to receive data. Data may arrive at the component before the instruction to transition to the RUN state (though this is expected to be rare). The component should treat that data as if it were received in the RUN state.
  • RUN: Components should expect to receive data. Data should not be produced in any other state.

To mark the start and end of a run in the data flow, the producer.py script produces INFO messages with contents "Beginning run" and "Ending run", respectively.

Operator

The LArPix DAQ Operator module provides the interface into the DAQ core for all DAQ operations.

Operator methods interact with the DAQ core to accomplish the desired behavior. For the simplest interactions, a single request and response exchange occurs, and the result is returned. (TODO!!! unify this interface) For most interactions, there are multiple responses for a single request - e.g. an immediate acknowledgement of receipt and then the eventual result. The methods implementing these interactions return generator iterators rather than values. The way to call these functions usually looks like

o = Operator()
final_responses = []
for response in o.run_routine('example'):
    print(response)
    # interact with response object within loop
# When the loop ends, the last response received is still saved in
# the response object
final_responses.append(response)

Metadata

Release files for larpix-daq 0.2.0rc5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for larpix-daq 0.2.0rc5
File Size Uploaded Provenance Actions
larpix-daq-0.2.0rc5.tar.gz 19.3 kB Without provenance Details for larpix-daq-0.2.0rc5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for larpix-daq 0.2.0rc5
File Interpreter ABI Platform Actions
larpix_daq-0.2.0rc5-py3-none-any.whl Python 3 none any Details for larpix_daq-0.2.0rc5-py3-none-any.whl

Total release size: 43.0 kB

Release files / larpix-daq-0.2.0rc5.tar.gz

Download URL larpix-daq-0.2.0rc5.tar.gz
Size 19.3 kB
Tags Source
SHA-256 checksum
How to use checksums
5ac8fcfdccfdfa4988870d89c72fb4944965fea9d6099adfbb8e33c4c70cb318
BLAKE2b-256 checksum
How to use checksums
ce3362cdd45b686939325ed14be319321e34b398142176877ebb6f1e784a4af4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.19.4 CPython/3.6.4

Release files / larpix_daq-0.2.0rc5-py3-none-any.whl

Download URL larpix_daq-0.2.0rc5-py3-none-any.whl
Size 23.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2fbccf45d073af98d7e20b42ca703f01088e0bb23d0460b50d00c550a13557fe
BLAKE2b-256 checksum
How to use checksums
bca6278213c99750adbc6f410cc7829b9c120acf5865b86eba6b1d0387cbf31a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.19.4 CPython/3.6.4

Security for larpix-daq 0.2.0rc5

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page