Difference between revisions of "SAMPA SRO"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
=== Configuration and running === | === Configuration and running === | ||
| − | + | 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` to run the services locally (running on a farm will require artifacts | |
| − | + | being accessible on every farm node). | |
| − | + | The shell 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 | ||
| + | |||
| + | You can put the above shell commands into a script ( e.g. jana.ersap) and run the script instead. | ||
| + | To do that you can use ERSAP CLI (ersap-shell) | ||
| + | |||
| + | #*> $ERSAP_HOME/bin/ersap-shell jana.ersap | ||
Revision as of 20:15, 8 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
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` to run the services locally (running on a farm will require artifacts being accessible on every farm node). The shell 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
You can put the above shell commands into a script ( e.g. jana.ersap) and run the script instead. To do that you can use ERSAP CLI (ersap-shell)
- > $ERSAP_HOME/bin/ersap-shell jana.ersap