Skip to content
Snippets Groups Projects

Validate DaVinci configuration for Turbo data

Merged Alex Pearce requested to merge apearce-validate-turbo-configuration into master
All threads resolved!

Ensure that DaVinci() is configured correctly if Turbo = True, throwing an exception if not.

Triggered by discussion in LHCb!954 (merged).

/cc @cattanem

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
  • Alex Pearce added 1 commit

    added 1 commit

    Compare with previous version

  • Alex Pearce resolved all discussions

    resolved all discussions

  • @apearce, reading the discussion in the related MR in LHCb: I should cherry-pick this MR into all 3 201X-patches branches, correct? it was not explicitly requested but seems best to me. Can you confirm, just to make sure I am not missing a subtlety? Thanks a lot.

  • mentioned in commit b715c5a0

  • mentioned in commit 8af5af2c

  • Eduardo Rodrigues mentioned in merge request !123 (merged)

    mentioned in merge request !123 (merged)

  • Hi @apearce, I cherry-picked to 2018-patches but things did not work for 2016-patches. Trying to do things manually I noticed that I could not "cherry-pick" this MR to 2016-patches since the DaVinci Configuration.py file does not actually know about TurboConf nor has a "Turbo" property. So it seems there is much more to update there. Shall we discuss this when you have time? For now I'm proceeding with my stacks ...

    Edited by Eduardo Rodrigues
  • Please register or sign in to reply
    Loading