Open adfrawley opened 9 hours ago
Report for commit b85f848f31ab683810de250a38500e6c6303c98e:
gcc-12.1.0
/ clang
is SUCCESS, :bar_chart:clang report (full)/(new), build loggcc-12.1.0
/ new
is SUCCESS, :bar_chart:Compiler report (full)/(new), build log
gcc-12.1.0
, build new
: run the default sPHENIX macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default CaloProduction/Fun4All_Year1.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of CaloProduction/Fun4All_Year1.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of CaloProduction/Fun4All_Year2.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of StreamingProduction/Fun4All_Stream_Combiner.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: run the overlap check for sPHENIX macro: build is SUCCESS, output gcc-12.1.0
, build new
: Valgrind test: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:gcc-12.1.0
/ scan
is SUCCESS, :bar_chart:scan-build report (full)/(new), build logclang-tidy
is UNSTABLE, :bar_chart:clang-tidy
report (full)/(new)cpp-check
is SUCCESS, :bar_chart:cppcheck
report (full)/(new)_Automatically generated by sPHENIX Jenkins continuous integration_
Types of changes
What kind of change does this PR introduce? (Bug fix, feature, ...)
Add the ability to PHSimpleVertexFinder to find collision vertices for zero field data. Finds SvtxTracks on the node tree. Gets the clusters for the silicon seed (if existing). Gets the clusters for the TPC seed (if existing). Fits all the found clusters with a straight line. Calculates PCA for all pairs of straight line tracks in the track map, and selects close matches. Then runs the same vertex finding procedure as for field on tracks. The zero field option is enabled by setting a flag in the macro (default is false): finder->zeroField(true);
TODOs (if applicable)
Links to other PRs in macros and calibration repositories (if applicable)