Skip to content
Snippets Groups Projects

Remove old RICH framework + Future scalar algorithms

Merged Christopher Rob Jones requested to merge jonrob/Rec:Rich-RemoveOldFramework into master
  • Removes all the code related to the old RICH framework.
  • Removes scalar implementations of various future algorithms, now replaced with SIMD versions.
Edited by Marco Cattaneo

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Part of the problem is I think I accidentally committed some fixes needed here to !821 (closed). As these two MRs are not really that different in nature, I think the easiest fix is I merge them into one.

    Edited by Christopher Rob Jones
  • added 5 commits

    Compare with previous version

  • Christopher Rob Jones changed title from WIP Remove old RICH framework to WIP Remove old RICH framework + Future scalar algoruthms

    changed title from WIP Remove old RICH framework to WIP Remove old RICH framework + Future scalar algoruthms

  • Christopher Rob Jones changed the description

    changed the description

  • Christopher Rob Jones changed title from WIP Remove old RICH framework + Future scalar algoruthms to WIP Remove old RICH framework + Future scalar algorithms

    changed title from WIP Remove old RICH framework + Future scalar algoruthms to WIP Remove old RICH framework + Future scalar algorithms

  • mentioned in merge request Analysis!225 (merged)

  • @jonrob There is still an issue in the Brunel Expert monitoring sequence, see brunel-mc11a-xdst test:

    ExpertProtoMoni      INFO Member list: ChargedProtoParticleTupleAlg/ChargedProtoTuple, ANNGlobalPID::ChargedProtoANNPIDTrainingTuple/ChargedProtoPIDANNTuple, with context 'Offline'
    ToolSvc             ERROR Cannot create tool Rich::Rec::MC::MCTruthTool (No factory found)
    ChargedProtoTuple   FATAL ChargedProtoParticleTupleAlg:: Exception throw: tool():: Could not retrieve Tool 'Rich::Rec::MC::MCTruthTool'/'MCTruth' StatusCode=FAILURE
    ChargedProtoTuple   FATAL  Exception with tag= is caught 
    ChargedProtoTuple   ERROR 	ChargedProtoTuple:: tool():: Could not retrieve Tool 'Rich::Rec::MC::MCTruthTool'/'MCTruth'	 StatusCode=FAILURE
    ExpertProtoMoni     ERROR GaudiSequencer:: Can not initialize ChargedProtoTuple StatusCode=FAILURE
  • Damn, I forgot about checking expert mode. Will take a look.

  • mentioned in merge request LHCb!1027 (merged)

  • added 1 commit

    • 57b2cf62 - Update ChargedProtoANNPID and GlobalReco to adapt to removal of Rich Rec MCTruth tool

    Compare with previous version

  • Fixed. The issue was whilst I had removed the implementation of an MC truth tool in Rec I had neglected to remove the interface for it in LHCb. Consequently a few (non RICH) components in which I had used the RICH tool (for convenience...) where still being built against it, but of course then failed to find the component at runtime.

    LHCb!1027 (merged) and Lbcom!203 (merged) remove the interface, and port to the remaining lower level MC truth tool the one method they used, which was for Track to MCParticle associations. Eventually the components (ChargedProtoANNPID and GlobalReco) will anyway need to be modernised for the upgrade, but this keeps them going in the meantime.

  • mentioned in merge request Panoramix!13 (merged)

  • mentioned in commit LHCb@297c8094

  • Marco Cattaneo unmarked as a Work In Progress

    unmarked as a Work In Progress

  • removed lhcb-clang-test ~1280 labels

  • Marco Cattaneo resolved all discussions

    resolved all discussions

  • Marco Cattaneo mentioned in commit ad233bf3

    mentioned in commit ad233bf3

  • Marco Cattaneo mentioned in merge request Brunel!335 (merged)

    mentioned in merge request Brunel!335 (merged)

  • @jonrob This MR is breaking Panoptes (which I think you are aware of) but also Panoramix. Could you have a look please?

  • I already have MRs fixing both submitted.

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading