-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Prologue: if you just want to see something run, and you’re on a system which is artdaq-ready, execute these commands:
baseurl="https://raw.githubusercontent.com/art-daq/artdaq-demo/refs/heads/develop/tools"
target=$(curl -s "$baseurl/quick-spack-start.sh") # Link to actual script
curl "$baseurl/$target" -o quick-spack-start.sh
chmod +x quick-spack-start.sh
./quick-spack-start.sh # get latest
OR
./quick-spack-start.sh --develop
Then
source setupARTDAQDEMO
-
to list versions: ls /cvmfs/fermilab.opensciencegrid.org/products/artdaq/spack_*
- Each supported Spack version has its own directory containing product directories (e.g. spack_v0.28/artdaq-v4_05_00)
- These (or local Spack areas) can be included using the --upstream argument to quick-spack-start.sh
-
check for and remove ~/.spack if there are problems or if you want to be proactive.
-
The install script creates two setup scripts:
setupARTDAQDEMOgets your environment ready for running artdaq. To do Spack development tasks, usesetup-env.sh, which does not set up the artdaq build envrionment.
…to execute the downloading, building, and the running of the demo; the total space taken will be about 9 GB. Installation on Fermilab hosts takes about 5 minutes, though on other systems this may take longer depending on connection speed. A few windows will pop up to show sample monitoring of the fake data produced during the demo; you can just close them manually when the demo’s done.
This project demonstrates how the toolkit comprised of the artdaq and artdaq-core packages can be used to build the DAQ software for an experiment by providing a simple example system. Attached at the bottom of the page is some useful but potentially dated documentation; for up-to-date information, use the following Wiki links, starting with “A description of the demo system” :
- A description of the demo system
- Installing and building the demo
- (Re)building the artdaq-demo package
- Running a sample artdaq-demo system
- A closer look - TRACEs and configuring
- How to write a fragment generator
- How to write an overlay class
- Filtering, analyzing, and presenting your raw events: a closer look at art modules
- [[Creating an art module which saves the build time and version of your package]]
- The artdaq-demo Examples
- Creating a new Fragment type
- artdaq in VM or container, etc.
- Requirements for artdaq Demo
Setting up an artdaq-demo development area with MRB
artdaq-demo Release Notes
artdaq-demo-hdf5