You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PyBAR is a versatile readout and test system for the ATLAS FEI4(A/B) pixel readout chip. It uses the [basil](https://github.com/SiLab-Bonn/basil) framework to access the readout hardware.
7
7
PyBAR's FPGA firmware and host software includes support for different hardware platforms.
8
8
9
-
PyBAR is *not only* targeting experienced users and developers. The easy-to-use scripts allow a quick setup and start. PyBAR is a very flexible readout and test system and provides the capability to conduct tests and characterization measurements of individual chips.
9
+
PyBAR is *not only* targeting experienced users and developers. The easy-to-use scripts allow a quick setup and start. PyBAR is a very flexible readout and test system and provides the capability to conduct tests and characterization measurements of individual chips, and tests of large-scale detectors with multiple multi-chip modules and multiple readout boards.
10
10
11
11
The features of the FPGA firmware in a nutshell:
12
12
- supported readout boards:
13
13
any hardware that is supported by basil (e.g., MIO2, MIO3, and MMC3)
14
14
- supported adapter cards:
15
15
Single Chip Adapter Card, Burn-in Card (Quad Module Adapter Card) and the General Purpose Analog Card (GPAC)
16
-
- readout of single chip modules
16
+
- readout of multiple readout boards
17
+
- readout of multiple multi-chip modules (e.g., single, dual, quad module, and any combination of those)
18
+
- simultaneous readout (e.g., data taking with external trigger, individual tuning of chips)
17
19
- continuous data taking
18
-
- automatic data to clock phase alignment
20
+
-individual and automatic data to clock phase alignment on each channel
19
21
- full support of EUDAQ TLU and availability of EUDAQ Producer
20
22
21
23
The features of the host software in Python:
22
24
- no GUI
23
25
- support for Windows, Linux and macOS
24
26
- scan/tuning/calibration algorithms are implemented in stand-alone scripts
27
+
- scripts are implemented for operating single chips but are working with multi-chip configurations as well
25
28
- fast development and implementation of new scan/tuning/calibration algorithms
26
29
- configuration files are human readable (compatible to RCE/HSIO)
27
30
- full control over FEI4 command generation, sending any arbitrary bit stream and configuration sequence to the FEI4
@@ -33,7 +36,7 @@ The features of the host software in Python:
33
36
34
37
The following packages are required for pyBAR's core functionality:
Copy file name to clipboardExpand all lines: examples/example_run_manager/example_run_manager.py
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
# The initial FE configuration will be created during the first run.
10
10
#
11
11
# (from configuration.yaml)
12
-
# fe_flavor : fei4a
12
+
# flavor : fei4a
13
13
# ...
14
14
#
15
15
# Initializing the run manager:
@@ -18,17 +18,17 @@
18
18
# During the first run, an module data directory relative to the configuration.yaml file will be created.
19
19
# If configuration.yaml is placed inside /host/pybar/ the module data will be stored inside /host/pybar/<module_id> (where <module_id> is defined inside configuration.yaml).
20
20
#
21
-
# If fe_configuration inside configuration.yaml is not given, the latest valid FE configuration file will be taken (the file with the highest run number and run status 'FINISHED').
21
+
# If configuration inside configuration.yaml is not given, the latest valid FE configuration file will be taken (the file with the highest run number and run status 'FINISHED').
22
22
#
23
23
# (from configuration.yaml)
24
-
# fe_configuration:
24
+
# configuration:
25
25
# ...
26
26
#
27
-
# If no configuration file exists, a initial configuration will be create according to fe_flavor.
27
+
# If no configuration file exists, a initial configuration will be create according to flavor.
28
28
# To load a specific configuration file, a path to FE configuration file or a run number (e.g. 5) can be given:
29
29
#
30
30
# (from configuration.yaml)
31
-
# fe_configuration: 1
31
+
# configuration: 1
32
32
# ...
33
33
#
34
34
# This will retain the configuration for the following scans.
0 commit comments