No description
8dfa2d798a
Speed is great: it's faster when using the root-histogram plugin. In the case of the cpp-test plugin, which does not do anything, it's slower: 6 GB/s vs 9 GB/s when running the plugin directly. -> As soon as a bit of work is done per event it should always be better to buffer up parsed event data and process it in a tight loop (in a different thread). |
||
|---|---|---|
| .vscode | ||
| cmake | ||
| data | ||
| external | ||
| include/mesytec-mnode | ||
| proto | ||
| python | ||
| src | ||
| .clang-format | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| README.md | ||
mesytec-mnode
How to build
Assumes git, ninja, cmake, gcc or clang. If under msys2 use ucrt64.
protobuf is required. Use the same compiler for protobuf and mesytec-mnode.
git clone --depth 1 https://github.com/protocolbuffers/protobuf --branch v3.29.2 --shallow-submodules --recurse-submodules=third_party/abseil-cpp
mkdir -p protobuf/build && cd protobuf/build && cmake -GNinja -DCMAKE_BUILD_TYPE=Release -Dprotobuf_BUILD_TESTS=OFF -DCMAKE_INSTALL_PREFIX=~/local/protobuf .. && cmake --build . -j && cmake --install .; cd -
export CMAKE_PREFIX_PATH=~/local/protobuf
git clone mesytec-mnode and cd into it.
cd mesytec-mnode
git submodule update --init --recursive
mkdir build && cd build && cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=~/local/mesytec-mnode .. && cmake --build . -j && ctest . && cmake --install .