Skip to content
Snippets Groups Projects

Reopen !1772 (Tests for GaudiAllen)

Merged Reopen !1772 (Tests for GaudiAllen)
2 unresolved threads
Merged Marian Stahl requested to merge mstahl_gaudiallentests into master
2 unresolved threads

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
4
5 This software is distributed under the terms of the GNU General Public
6 Licence version 3 (GPL Version 3), copied verbatim in the file "COPYING".
7
8 In applying this licence, CERN does not waive the privileges and immunities
9 granted to it by virtue of its status as an Intergovernmental Organization
10 or submit itself to any jurisdiction.
11 -->
12 <!--
13 Run Allen VeloUT tracking and apply PrTrackChecker MC tracking efficiency
14 checker.
15 -->
16 <extension class="GaudiTest.GaudiExeTest" kind="test">
17 <argument name="program"><text>gaudirun.py</text></argument>
18 <argument name="args"><set>
19 <text>$MOOREROOT/tests/options/default_input_and_conds_hlt1_retinacluster_FTv6.py</text>
  • You set up some number of events in this file, but you also set number of events in the option file you are calling below and that number of events will then be processed, I think (as it the latest change of the settings.)

  • Please register or sign in to reply
  • 1 1 ###############################################################################
    2 # (c) Copyright 2019 CERN for the benefit of the LHCb Collaboration #
    2 # (c) Copyright 2021 CERN for the benefit of the LHCb Collaboration #
    • Hello @mstahl, I found this MR just now, unfortunately it broke some Allen monitoring jobs we have.

      Looking on all the new option files, which one now should be used for the regular Allen (called from Moore) data challenges tests? allen_gaudi_seed_and_match, allen_gaudi_forward or even better, run both of them an then results could be compared with each other (personally I would got with this option, but maybe not really needed?)?.

    • Author Developer

      Hi @msaur! Sorry, I wasn't aware. Where are the jobs configured? If possible, I'd propose to run both allen_gaudi_seed_and_match and the hlt1_hlt2_comparison (there's no test for this at the moment; I can add one next week, and also correct the options files for the number of events). The latter is equivalent to hlt1_pp_default of Allen and runs the forward tracking, while allen_gaudi_seed_and_match runs seeding and matching, currently without UT.

    • Hello @mstahl, thanks for details, we will try to run those new jobs (we are using LHCbPR and all the jobs are defined in PRConfig) and if any issue we would go back to you.

    • Please register or sign in to reply
  • mentioned in issue #485 (closed)

  • Marian Stahl mentioned in merge request !1826 (closed)

    mentioned in merge request !1826 (closed)

  • mentioned in issue #487 (closed)

  • Please register or sign in to reply
    Loading