gwm17/SPS_SABRE_EventBuilder
1
0
Fork 0
mirror of https://github.com/sesps/SPS_SABRE_EventBuilder.git synced 2024-11-26 19:38:50 -05:00
Code Issues Projects Releases Wiki Activity

Compare commits

base: gwm17:51d97d175595ad364bdbf8b1a3b53d88a9a45178
Branches Tags
gwm17:main
gwm17:devel
gwm17:compass_ver1.x
..
compare: gwm17:20f03b138338c90a0d175e093dad09f32939f1a4
Branches Tags
gwm17:devel
gwm17:main
gwm17:compass_ver1.x

No commits in common. "51d97d175595ad364bdbf8b1a3b53d88a9a45178" and "20f03b138338c90a0d175e093dad09f32939f1a4" have entirely different histories.
51d97d1755 ... 20f03b1383

1 changed files with 4 additions and 5 deletions
Show Stats Expand all files Collapse all files

7
README.md
View File

@ -12,12 +12,12 @@ cmake ..
make make
``` ```
To clone the repository use `git clone --recursive https://github.com/sesps/SPS_SABRE_EventBuilder.git`. The recursive flag is important; this tells github to pull all submodules associated with the repository. To clone the repository use `git clone --recursive https://github.com/sesps/SPS_SABRE_EventBuilder.git`. If you're using the devel branch be sure to specify this with the `--branch` flag. The recursive flag is important; this tells github to pull all submodules associated with the repository.
The binaries are installed to the `bin` directory of the event builder, and should be run from the event builder directory (i.e. `./bin/EventBuilderGui`). THe `bin` directory also contains a shell script named `archivist` for transferring data from a CoMPASS project to the The binaries are installed to the `bin` directory of the event builder, and should be run from the event builder directory (i.e. `./bin/EventBuilderGui`). THe `bin` directory also contains a shell script named `archivist` for transferring data from a CoMPASS project to the
event builder workspace. event builder workspace.
In general, one should only build for Release (this is the default), for maximum optimization. However, it can be useful to run in Debug (change the cmake command to `cmake -DCMAKE_BUILD_TYPE=Debug ..`) when testing new features. In general, one should only build for Release (this is the default), for maximum optimization. However, it can be useful to run in Debug (change the cmake command to `cmake -DCMAKE_BUILD_TYPE_DEBUG ..`) when testing new features.
## EventBuilder vs. EventBuilderGui ## EventBuilder vs. EventBuilderGui
There are two programs provided. They are `EventBuilderGui` and `EventBuilder`. The first is a full GUI version of the event builder. The GUI supports all conversion methods and the plotting tool. There are two programs provided. They are `EventBuilderGui` and `EventBuilder`. The first is a full GUI version of the event builder. The GUI supports all conversion methods and the plotting tool.
@ -27,7 +27,6 @@ For more information see the [wiki](https://github.com/sesps/SPS_SABRE_EventBuil
Additionally, check the [FAQ](https://github.com/sesps/SPS_SABRE_EventBuilder/wiki/FAQ) if you're having trouble with something. Additionally, check the [FAQ](https://github.com/sesps/SPS_SABRE_EventBuilder/wiki/FAQ) if you're having trouble with something.
## System Requirements ## System Requirements
- Requires C++17 - Requires ROOT version which supports CMake dictionary generation
- Requires ROOT version which supports CMake dictionary generation and is C++17 compatible
- Requires CMake >= 3.16 - Requires CMake >= 3.16
- This version is for data from CAEN CoMPASS >= 2.0. Data from older CoMPASS versions are not compatible. - This version is for data from CAEN CoMPASS >= 2.0. Data from older CoMPASS versions are not compatible.