Difference between revisions of "SAMPA SRO"
| Line 23: | Line 23: | ||
=== Configuration and running === | === Configuration and running === | ||
| − | + | '''Keeping the order of instructions are important''' | |
<br> | <br> | ||
NB. We recommend defining and creating $ERSAP_USER_DATA directory. No worries about the mentioned directory structure. After the first ERSAP execution the $ERSAP_USER_DATA directory will get proper structure. Use the ''ersap-shell'' (ERSAP CLI) to run the services locally. The CLI provides a high-level interface to configure and start the different ERSAP components required to run an application. | NB. We recommend defining and creating $ERSAP_USER_DATA directory. No worries about the mentioned directory structure. After the first ERSAP execution the $ERSAP_USER_DATA directory will get proper structure. Use the ''ersap-shell'' (ERSAP CLI) to run the services locally. The CLI provides a high-level interface to configure and start the different ERSAP components required to run an application. | ||
| Line 29: | Line 29: | ||
#Start the ERSAP shell: | #Start the ERSAP shell: | ||
#* $ERSAP_HOME/bin/ersap-shell | #* $ERSAP_HOME/bin/ersap-shell | ||
| − | # Define the application within a | + | # Define the application within a ''services.yaml'' file. An example of the file can be found in the ersap-jana installation manual. NB: The default location for the application definition file is in $ERSAP_USER_DATA/config dir |
#* ersap> set servicesFile services.yaml | #* ersap> set servicesFile services.yaml | ||
#Optionally you can change the number of parallel threads used by the services to process requests | #Optionally you can change the number of parallel threads used by the services to process requests | ||
Revision as of 12:44, 9 September 2021
Project dependencies
Installation
NB. For installation you should define ERSAP_HOME environmental variable.
Building SAMA DAQ codebase
NB. The package is kindly provided by the ALICE collaboration and is modified the EPSCI SRO group to make it streaming The modified package can be found at /home/gurjyan/Devel/stream/exp-sampa
- login into alkaloid.jlab.org
- copy the ALICE modified package into your own directory
- follow instructions in README to build the package
Configuration and running
Keeping the order of instructions are important
NB. We recommend defining and creating $ERSAP_USER_DATA directory. No worries about the mentioned directory structure. After the first ERSAP execution the $ERSAP_USER_DATA directory will get proper structure. Use the ersap-shell (ERSAP CLI) to run the services locally. The CLI provides a high-level interface to configure and start the different ERSAP components required to run an application.
- Start the ERSAP shell:
- $ERSAP_HOME/bin/ersap-shell
- Define the application within a services.yaml file. An example of the file can be found in the ersap-jana installation manual. NB: The default location for the application definition file is in $ERSAP_USER_DATA/config dir
- ersap> set servicesFile services.yaml
- Optionally you can change the number of parallel threads used by the services to process requests
- ersap> set threads <NUM_THREADS>
- Start the data processing. This will start the main Java DPE, a C++ DPE if the C++ service is listed in `services.yaml`,and it will run the streaming orchestrator to process the data-stream.
- ersap> run local
- Run SAMPA DAQ (on some other terminal)
- >source [modified ALICE code directory]/dist/trorc/trorc-operator/setenv.sh
- >treadout --data-type 1 --frames 2000 --mode das --mask 0x1 --events 0
For more on SAMPA DAQ configuration read the README in the ALICE code directory.