47287 was the first run2pp physics run passing our 5minute cut

[pinkenburg]

Types of changes

• [ X] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work for users)
• Requiring change in macros repository (Please provide links to the macros pull request in the last section)
• I am a member of GitHub organization of sPHENIX Collaboration, EIC, or ECCE (contact Chris Pinkenburg to join)

What kind of change does this PR introduce? (Bug fix, feature, ...)

This PR changes the first run2pp physics run from 47286 to 47287. Run 47286 is just 30 seconds long and is therefore not among the reconstructed run2pp runs

TODOs (if applicable)

Links to other PRs in macros and calibration repositories (if applicable)

Motivation / Context

Run 47286 was initially identified as the first Run 2 proton-proton physics run but was only 30 seconds in duration, failing to meet the established reconstruction criteria for Run 2 datasets. sPHENIX requires Run 2 proton-proton physics runs to satisfy a minimum 5-minute duration threshold and accumulate at least 100k events. Run 47287 is the first run that meets these quality standards.

Key Changes

• Updated RUN2PP_FIRST constant in RunnumberRange.h from 47286 to 47287
• This adjusts the run-number boundary definition for identifying Run 2 proton-proton physics data in downstream reconstruction and analysis code
• File: offline/framework/phool/RunnumberRange.h (+2/-2 lines)

Potential Risk Areas

• Reconstruction behavior: Any code that filters or selects Run 2 proton-proton data using RUN2PP_FIRST will now exclude run 47286, potentially affecting:
  • Existing datasets indexed by run number ranges
  • Analysis workflows that explicitly include early runs in this period
  • Calibration procedures tied to specific run ranges
• Data consistency: Validation of run-selection logic across the collaboration's analysis framework should ensure consistency with this new boundary

Possible Future Improvements

• Document run 47286's exclusion in data quality notes to ensure analysis teams are aware of the gap
• Consider automated validation checks in reconstruction that verify runs meet the stated quality criteria (≥5 minutes, ≥100k events)

---

Note: This summary is AI-generated and should be cross-checked against the actual code changes. Use your best judgment when reviewing critical data selection logic.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e21f2a69-07d0-4731-84c7-678922a679fc

📥 Commits

Reviewing files that changed from the base of the PR and between e7a8cb6 and 91da544.

📒 Files selected for processing (1)

• offline/framework/phool/RunnumberRange.h

---

📝 Walkthrough

Walkthrough

The PR updates the RUN2PP_FIRST constant in RunnumberRange.h from 47286 to 47287, adjusting the inclusive first-run boundary for the RUN2PP data-taking period.

Changes

RUN2PP Run Number Boundary

Layer / File(s)	Summary
Run Number Constant Update offline/framework/phool/RunnumberRange.h	RUN2PP_FIRST constant is incremented from 47286 to 47287 to update the run-number boundary.

Possibly related PRs

• sPHENIX-Collaboration/coresoftware#4224: Prior PR modified the same symbol in RunnumberRange.h, changing RUN2PP_FIRST to constexpr with value 47286; this PR updates its value to 47287.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sphenix-jenkins-ci]

Build & test report

Report for commit 91da54406caacad9b07ac43f68b4bc4d3142ffa4:

• builds and tests overall are SUCCESS.
• Build with configuration of alma9.2-gcc-14.2.0 / clang is SUCCESS, 📊clang report (full)/(new), build log
• Build with configuration of alma9.2-gcc-14.2.0 / new is SUCCESS, 📊Compiler report (full)/(new), build log
  • Generating DST and readback: build is SUCCESS
  • Calorimeter QA: build is SUCCESS, 📊 trends
    • 📊 QA-calorimeter for e- at p_T=4GeV : combined Chi2/nDoF = 27.45 / 72, and combined p-Value = 1
    • 📊 QA-calorimeter for pi+ at p_T=30GeV : combined Chi2/nDoF = 41.7331 / 72, and combined p-Value = 0.99837
    • 📊 QA-calorimetric-jet for e- at p_T=4GeV : combined Chi2/nDoF = 0.4559 / 42, and combined p-Value = 1
    • 📊 QA-calorimetric-jet for pi+ at p_T=30GeV : combined Chi2/nDoF = 14.2531 / 42, and combined p-Value = 0.999981
  • Tracking QA with Distortions: build is SUCCESS, 📊 trends
    • 📊 QA-distortions
  • Tracking QA at low occupancy: build is SUCCESS, 📊 trends
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
    • 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • 📊 QA-Tpc : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • 📊 QA-tracking : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • 📊 QA-vertexing : combined Chi2/nDoF = 30 / 112, and combined p-Value = 1
  • Tracking QA for Pythia D0-jet: build is SUCCESS, 📊 trends
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
    • 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • 📊 QA-Tpc : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • 📊 QA-tracking : combined Chi2/nDoF = -0 / 50, and combined p-Value = 1
    • 📊 QA-vertexing : combined Chi2/nDoF = 30 / 112, and combined p-Value = 1
  • Tracking QA from run2pp 53877: build is SUCCESS, 📊 trends
    • 📊 QA-intt : combined Chi2/nDoF = -0 / 18, and combined p-Value = 1
    • 📊 QA-micromegas : combined Chi2/nDoF = -0 / 6, and combined p-Value = 1
    • 📊 QA-mvtx : combined Chi2/nDoF = -0 / 18, and combined p-Value = 1
    • 📊 QA-siliconseeds : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
    • 📊 QA-tpc : combined Chi2/nDoF = -0 / 48, and combined p-Value = 1
    • 📊 QA-tpcseeds : combined Chi2/nDoF = 3.33163e-06 / 28, and combined p-Value = 1
    • 📊 QA-trackfit : combined Chi2/nDoF = 3.00663 / 32, and combined p-Value = 1
  • system alma9.2-gcc-14.2.0, build new: run the default sPHENIX macro: build is SUCCESS, output, trends 📊
  • system alma9.2-gcc-14.2.0, build new: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends 📊
  • system alma9.2-gcc-14.2.0, build new: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends 📊
  • system alma9.2-gcc-14.2.0, build new: Valgrind test of CaloProduction/Fun4All_Year2.C: build is SUCCESS, 📊valgrind report, trends 📊
  • system alma9.2-gcc-14.2.0, build new: Valgrind test of StreamingProduction/Fun4All_Stream_Combiner.C: build is SUCCESS, 📊valgrind report, trends 📊
  • system alma9.2-gcc-14.2.0, build new: run the overlap check for sPHENIX macro: build is SUCCESS, output
  • system alma9.2-gcc-14.2.0, build new: Valgrind test: build is SUCCESS, 📊valgrind report, trends 📊
• Build with configuration of alma9.2-gcc-14.2.0 / scan is SUCCESS, 📊scan-build report (full)/(new), build log
• clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
• cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration