Skip to content

Commit 74a3a78

Browse files
aphecetchektf
aphecetche
authored and
ktf
committed
[O2-621] Rename executable digitizer-workflow to
o2-sim-digitizer-workflow
1 parent 9b55c1e commit 74a3a78

File tree

6 files changed

+19
-19
lines changed

6 files changed

+19
-19
lines changed

‎Detectors/ITSMFT/ITS/macros/test/run_test.sh‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ mcGener=boxgen
1010
o2sim -n $nEvents -e $mcEngine -g $mcGener -m PIPE ITS >& sim_its.log
1111

1212
# Digitizing in triggered readout mode...
13-
digitizer-workflow --configKeyValues "ITSDigitizerParam.continuous=0" >& digi.log
13+
o2-sim-digitizer-workflow --configKeyValues "ITSDigitizerParam.continuous=0" >& digi.log
1414

1515
root.exe -b -q CheckDigits.C+ >& CheckDigits.log
1616

‎Detectors/ITSMFT/ITS/macros/test/run_workflows.sh‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
#!/bin/bash
22
o2sim -n 10 -e TGeant3 -g boxgen -m PIPE ITS >& sim.log
3-
digitizer-workflow >& digi.log
4-
#digitizer-workflow --configKeyValues "ITSDigitizerParam.continuous=0" >& digi.log
5-
its-reco-workflow >& reco.log
3+
o2-sim-digitizer-workflow >& digi.log
4+
#o2-sim-digitizer-workflow --configKeyValues "ITSDigitizerParam.continuous=0" >& digi.log
5+
o2-its-reco-workflow >& reco.log
66

77
# These macros can be run to check the quality of the results
88
# root.exe CheckDigits.C+

‎Detectors/TPC/workflow/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The digitizer workflow produces the file `tpcdigits.root` by default, data is st
3434
all sectors.
3535

3636
The workflow can be run starting from digits, raw clusters, or (native) clusters, or directly attached to the
37-
`digitizer-workflow`, see comment on inputs types below.
37+
`o2-sim-digitizer-workflow`, see comment on inputs types below.
3838

3939
### Quickstart running the reconstruction workflow
4040
The workflow is implemented in the `tpc-reco-workflow` executable.

‎Steer/DigitizerWorkflow/CMakeLists.txt‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ O2_SETUP(NAME ${MODULE_NAME})
1818
set(BUCKET_NAME ${MODULE_BUCKET_NAME})
1919

2020
O2_GENERATE_EXECUTABLE(
21-
EXE_NAME digitizer-workflow
21+
EXE_NAME o2-sim-digitizer-workflow
2222

2323
SOURCES
2424
src/SimpleDigitizerWorkflow.cxx

‎Steer/DigitizerWorkflow/README.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ This is a short documention for the DPL-DigitizerWorkflow example
44

55
# Status/Description of implementation
66

7-
At present, the `digitizer-workflow` executable is a demonstrator of
7+
At present, the `o2-sim-digitizer-workflow` executable is a demonstrator of
88
how we intend to do initiate and handle the processing of hits, coming from detector simulation.
99

10-
The digitizer-workflow currently demonstrates the transformation of hits into TPC digits using
10+
The `o2-sim-digitizer-workflow` currently demonstrates the transformation of hits into TPC digits using
1111
realistic bunch crossing and collision sampling. We are also able to overlay hits from background and signal hit inputs.
1212

13-
The main components of the digitizer-workflow are
13+
The main components of the `o2-sim-digitizer-workflow` are
1414

1515
* The SimReader device:
1616
- reading/analysing the given hit files
@@ -21,11 +21,11 @@ The main components of the digitizer-workflow are
2121
- producing digits in continuous time for a given sector
2222
- at present writes (or forwards) these digits in units of TPC drift times
2323

24-
The digitizer-workflow executable is already somewhat configurable, both in terms of
24+
The `o2-sim-digitizer-workflow` executable is already somewhat configurable, both in terms of
2525
workflow/topology options as well as individual device options. Some help is available
2626
via
2727
```
28-
digitizer-workflow --help
28+
o2-sim-digitizer-workflow --help
2929
```
3030
Other features are demonstrated in he following section.
3131

@@ -34,34 +34,34 @@ Other features are demonstrated in he following section.
3434
Let's assume we have a background hit file `o2sim_bg.root` generated
3535
by the O2 simulation with
3636
```
37-
o2sim -n 20 -g SOMEBACKGROUNDEVENTGENERATOR -m [detectors] -o o2sim_bg.root
37+
o2-sim -n 20 -g SOMEBACKGROUNDEVENTGENERATOR -m [detectors] -o o2sim_bg.root
3838
```
3939

4040
Similar for a signal file `o2sim_sg.root`
4141
```
42-
o2sim -n 50 -g SOMESIGNALEVENTGENERATOR -m [detectors] -o o2sim_sg.root
42+
o2-sim -n 50 -g SOMESIGNALEVENTGENERATOR -m [detectors] -o o2sim_sg.root
4343
```
4444

4545
1. **How can I digitize all sectors for the given background event?**
4646
```
47-
digitizer-workflow -b --simFile o2sim_bg.root
47+
o2-sim-digitizer-workflow -b --simFile o2sim_bg.root
4848
```
4949
This will run as many TPC digitizer processors as there are logical CPU cores on your machine in parallel.
5050
(Note that depending on your available memory, this might cause problems as the digitization needs lots of memory; It might be safer to start with a small number of workers as indicated under point 3.).
5151

5252
2. **How can I only digitize sectors TPC sectors 1 + 2 for the given background event?**
5353
```
54-
digitizer-workflow -b --tpc-sectors=1,2 --simFile o2sim_bg.root
54+
o2-sim-digitizer-workflow -b --tpc-sectors=1,2 --simFile o2sim_bg.root
5555
```
5656

5757
3. **How can I digitize sectors 1-8 using only 2 TPC digitizer devices?**
5858
```
59-
digitizer-workflow -b --tpc-lanes=2 --tpc-sectors=1,2,3,4,5,6,7,8 --simFile o2sim_bg.root
59+
o2-sim-digitizer-workflow -b --tpc-lanes=2 --tpc-sectors=1,2,3,4,5,6,7,8 --simFile o2sim_bg.root
6060
```
6161

6262
4. **How can I digitize a total of 100 sampled collisions merging background and signal hits for TPC sector 1?**
6363
```
64-
digitizer-workflow -b --tpc-sectors=1 --simFile o2sim_bg.root --simFileS o2sim_sg.root -n 100
64+
o2-sim-digitizer-workflow -b --tpc-sectors=1 --simFile o2sim_bg.root --simFileS o2sim_sg.root -n 100
6565
```
6666

6767
# Missing things/Improvements to come

‎doc/DetectorSimulation.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Detector simulation, the simulation of detector response from virtual particle e
1010
a) the generation of simple (energy deposit) traces in the detector due to the passage of particles and the interaction with the detector material.
1111
b) the conversion of those traces into (electronic) signals in the detector readout (usually called digitization).
1212

13-
The first part is handled by the `o2-sim` executable. The second part is handled in the `digitizer-workflow`.
13+
The first part is handled by the `o2-sim` executable. The second part is handled in the `o2-sim-digitizer-workflow`.
1414

1515
# Documentation of `o2-sim`
1616

@@ -102,4 +102,4 @@ This will produce a file `MCStepLoggerOutput.root` containing detailed informati
102102

103103
## Development
104104

105-
# Documentation of `digitizer-workflow`
105+
# Documentation of `o2-sim-digitizer-workflow`

0 commit comments

Comments
 (0)