Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Analysis Analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCbLHCb
  • AnalysisAnalysis
  • Issues
  • #26
Closed
Open
Issue created Jan 27, 2022 by Sascha Stahl@sstahlDeveloper

FunTuple does not resolve data dependencies correctly

Data dependencies in functors like F.MINIPCHI2(v2_pvs) or F.MAP_INPUT(Functor=F.PT, Relations=DTFRelations) are not advertised to the data flow in the configuration. In the C++ this step correctly happens. As FunTuple has to be added explicitly to the control flow, the HiveDataBrokerSvc expects an input. However, the producers are not advertised to the HiveDataBrokerSvc and the initialization fails, see for example message in https://mattermost.web.cern.ch/lhcb/pl/1ogine69tpnmmb8i9nxf543wih .

The examples in DaVinci work around this issue by adding algorithms to the control flow where it should not be necessary (example).

The likely problem is that the dictionary (or FunctorCollection) which contains the functors is not correctly parsed and the data dependencies are not identified. Some more description can also be found in LHCb#112 .

Edited Jan 27, 2022 by Sascha Stahl
Assignee
Assign to
Time tracking