Difference: ConnorsAnalysis-AnalysisTimeline (18 vs. 19)

Revision 192018-04-09 - ConnorGraham

Line: 1 to 1
 
META TOPICPARENT name="ConnorsAnalysis"
Return the the main analysis page.
Line: 19 to 19
 1. Update the version of the user directory files and start testing [in progress]

Copied over a recent version of Giuseppe's codes (after a full backup), we need to check that these all work as intended with 2017 data and check that these are the most recent versions of the codes (and check for any missing, new codes).

Changed:
<
<
  • Starting with a test run on just TrackAnalysis (responsible for track to sub-detector matching, but no cuts) and TwoPhotonAnalysis (responsible for the pi0 variables), with just GigaTrackerEvtReco as a pre-analyzer and with the usual dependency libraries. This was done with a single, reprocessed, 2017, golden run file; specifically run 8252, filtered for Pnn, bursts 13-15.
>
>
  • Critical codes to check: status of the framework revision you are using [updated but not checked for bug reports], status of the user directory background files [done by building a new user directory and starting from scratch], fullanalysis.conf and .settingsna62 files [in progress], HTCondor revision and file specifics [not started], any pre-analyzers required [just using GTK code for now], !TwoPhotonAnalysis.cc(.hh) [Giuseppe checking this], TrackAnalysis.cc(.hh) [Done timing and spacial plots look good], !OneTrackEventAnalysis.cc(.hh) [next], !KaonEventAnalysis.cc(.hh) [final step].
  • Starting with a test run on just TrackAnalysis (responsible for track to sub-detector matching, but no cuts) and TwoPhotonAnalysis (responsible for the pi0 variables), with just GigaTrackerEvtReco as a pre-analyzer and with the usual dependency libraries. This was done with a single, reprocessed, 2017, golden run file; specifically run 8252, filtered for Pnn, bursts 13-15. Files may be reprocessed again after the release of v0.11.2 (is CVMFS a better choce for final 2017 analysis?).
 
    • Initial results suggest timing issues in the CHOD as expected
Added:
>
>
    • After correcting CHODAnalysis.cc with the path to the newest light correction files this issue was resolved
 
  • Next we will add the OneTrackEventAnalysis code and test that
  • Later we will add KaonEventAnalysis and any new pre-analyzers

Using Kμ2 as a normalisation sample [done]

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback