Update DCA covariance and magnetic field

[osbornjd]

Types of changes

• 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 (contact Chris Pinkenburg to join)

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

This PR adds the feature to run the tracking with a constant magnetic field. This produces the best performance plots right now, as Acts assumes a constant field and may have a bug when it is interpreting the field map.

This PR also fixes a bug in the DCA uncertainty calculation. It now uses the rotated covariance matrix back from the Acts basis to the sPHENIX basis.

TODOs (if applicable)

Figure out why Acts has a difficult time interpreting our field map. That is for another PR.

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

Here is the macros PR which allows running the default Acts chain with either the PHTpcTracker or CASeeder, with either the constant or field map magnetic field.

[osbornjd]

BTW the performance plots that will be shown at the 10th sPHENIX collaboration meeting will correspond to the repository in the state given by this PR

[blackcathj]

There is a temp. problem on the main Jenkins server. The last check failed and let me check into it.

[blackcathj]

OK. Some change in the code introduced a stdout print as following that filled up the disks when QA simulation was launched ....

Global sPHENIX cov : 

0.408596, 0.0346545, -0.403718, 2.56428, 1.52273, 2.78078, 
0.0346545, 0.365808, -0.233651, -4.47635, -2.65696, -4.74909, 
-0.403718, -0.233651, 0.508482, 0.0457749, 0.026519, -0.00816996, 
2.56428, -4.47635, 0.0457749, 196.412, 115.842, 209.174, 
1.52273, -2.65696, 0.026519, 115.842, 68.324, 123.369, 
2.78078, -4.74909, -0.00816996, 209.174, 123.369, 222.771, 

Global sphenix cov after unit conv: 

0.00408596, 0.000346545, -0.00403718, 0.256428, 0.152273, 0.278078, 
0.000346545, 0.00365808, -0.00233651, -0.447635, -0.265696, -0.474909, 
-0.00403718, -0.00233651, 0.00508482, 0.00457749, 0.0026519, -0.000816996, 
0.256428, -0.447635, 0.00457749, 196.412, 115.842, 209.174, 
0.152273, -0.265696, 0.0026519, 115.842, 68.324, 123.369, 
0.278078, -0.474909, -0.000816996, 209.174, 123.369, 222.771, 

Initial Acts covariance: 

0.0346517, 0.000245753, 0.000169061, 8.02193e-07, -0.000337818, -0.000919993, 
0.000245753, 0.210222, 2.33445e-06, -0.000380771, -5.30305e-06, -0.141888, 
0.000169061, 2.33445e-06, 1.35012e-06, 3.73646e-09, -4.85983e-06, -6.40508e-06, 
8.02193e-07, -0.000380771, 3.73646e-09, 1.07328e-06, -6.71238e-09, 0.0002565, 
-0.000337818, -5.30305e-06, -4.85983e-06, -6.71238e-09, 4.03058e-05, 1.98045e-05, 
-0.000919993, -0.141888, -6.40508e-06, 0.0002565, 1.98045e-05, 1.09579, 

....

[osbornjd]

I made a mistake and forgot to turn the verbosity of the covariance matrix calculator to off (Tony notified me of this also). I pushed the change in this commit. Sorry for overwhelming Jenkins... but it should be fixed now and would just require restarting the build, I think.

Actually, it looks like Jenkins never restarted after I pushed the remove verbosity commit.

[sphenix-jenkins-ci]

Build & test report

Report for commit 8755fd489015c763ba1c31653af35abe2baf80c9:

• builds and tests overall are SUCCESS.
• Build with configuration of gcc-8.3 / new is SUCCESS, 📊Compiler report (full)/(new), build log
  • Generating DST and readback: build is SUCCESS
  • Calorimeter QA: build is SUCCESS
    • 📊 QA-calorimeter for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-calorimeter for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-calorimetric-jet for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
    • 📊 QA-calorimetric-jet for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
  • Tracking QA at high occupancy: build is SUCCESS
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • 📊 QA-Tpc : combined Chi2/nDoF = 280.651 / 56, and combined p-Value = 1.21608e-31
    • 📊 QA-tracking : combined Chi2/nDoF = 0.973577 / 26, and combined p-Value = 1
    • 📊 QA-vertexing : combined Chi2/nDoF = 1321.65 / 98, and combined p-Value = 2.04055e-213
  • Tracking QA at low occupancy: build is SUCCESS
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • 📊 QA-Tpc : combined Chi2/nDoF = 298.677 / 56, and combined p-Value = 7.84664e-35
    • 📊 QA-tracking : combined Chi2/nDoF = 53.6645 / 42, and combined p-Value = 0.107083
    • 📊 QA-vertexing : combined Chi2/nDoF = 1582.46 / 98, and combined p-Value = 2.65741e-266
  • system gcc-8.3, build new: run the default EICDetector macro: build is SUCCESS, output
  • system gcc-8.3, build new: run the default fsPHENIX macro: build is SUCCESS, output
  • system gcc-8.3, build new: run the default sPHENIX macro: build is SUCCESS, output
  • system gcc-8.3, build new: Valgrind test: build is UNSTABLE, 📊valgrind report
• Build with configuration of x8664_sl7 / clang is SUCCESS, 📊clang report (full)/(new), build log
• Build with configuration of x8664_sl7 / new is SUCCESS, 📊Compiler report (full)/(new), build log
• Build with configuration of x8664_sl7 / scan is SUCCESS, 📊scan-build report (full)/(new), build log
• cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration
           

[osbornjd]

@blackcathj I see a valgrind error but the page comes up blank with a java stack trace - was there an issue with Jenkins?

[blackcathj]

@blackcathj I see a valgrind error but the page comes up blank with a java stack trace - was there an issue with Jenkins?

Jenkins server was rebooted during the weekend which unfortunately wipe out the webpage format of previous reports. Nonetheless, we can always access the archived XML valgrind report as on the job summary page. As we have a large number of valgrind error at the moment, the XML report would be easier to search through

[sphenix-jenkins-ci]

Build & test report

Report for commit d5eb2af8e9f96a67efd8a310adf26b3ca92ce592:

• builds and tests overall are SUCCESS.
• Build with configuration of gcc-8.3 / new is SUCCESS, 📊Compiler report (full)/(new), build log
  • Generating DST and readback: build is SUCCESS
  • Calorimeter QA: build is SUCCESS
    • 📊 QA-calorimeter for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-calorimeter for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • 📊 QA-calorimetric-jet for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
    • 📊 QA-calorimetric-jet for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
  • Tracking QA at high occupancy: build is SUCCESS
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, 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 = 1.33499 / 38, and combined p-Value = 1
    • 📊 QA-vertexing : combined Chi2/nDoF = 1441.91 / 98, and combined p-Value = 1.02095e-237
  • Tracking QA at low occupancy: build is SUCCESS
    • 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, 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 / 42, and combined p-Value = 1
    • 📊 QA-vertexing : combined Chi2/nDoF = 2552.74 / 98, and combined p-Value = 0
  • system gcc-8.3, build new: run the default EICDetector macro: build is SUCCESS, output
  • system gcc-8.3, build new: run the default fsPHENIX macro: build is SUCCESS, output
  • system gcc-8.3, build new: run the default sPHENIX macro: build is SUCCESS, output
  • system gcc-8.3, build new: Valgrind test: build is UNSTABLE, 📊valgrind report
• Build with configuration of x8664_sl7 / clang is SUCCESS, 📊clang report (full)/(new), build log
• Build with configuration of x8664_sl7 / new is SUCCESS, 📊Compiler report (full)/(new), build log
• Build with configuration of x8664_sl7 / scan is SUCCESS, 📊scan-build report (full)/(new), build log
• cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration