Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
athena
Manage
Activity
Members
Labels
Plan
Jira
Code
Merge requests
154
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
atlas
athena
Commits
a09953c9
Commit
a09953c9
authored
1 year ago
by
Teng Jian Khoo
Browse files
Options
Downloads
Patches
Plain Diff
Add TODO comment
parent
9726ece2
Loading
Loading
1 merge request
!68125
ATR-28617: Rename FS LRT sequence to avoid clash with FS VSI
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Trigger/TriggerCommon/TriggerMenuMT/python/HLT/Config/ControlFlow/HLTCFConfig.py
+1
-0
1 addition, 0 deletions
...riggerMenuMT/python/HLT/Config/ControlFlow/HLTCFConfig.py
with
1 addition
and
0 deletions
Trigger/TriggerCommon/TriggerMenuMT/python/HLT/Config/ControlFlow/HLTCFConfig.py
+
1
−
0
View file @
a09953c9
...
...
@@ -451,6 +451,7 @@ def createDataFlow(flags, chains, allDicts):
filterOutput
=
[
CFNaming
.
filterOutName
(
filterName
,
inputName
)
for
inputName
in
filterInput
]
foundCFSeq
=
[
cfseq
for
cfseq
in
CFseqList
[
nstep
]
if
filterName
==
cfseq
.
filter
.
Alg
.
getName
()]
# TODO: Check sequence consistency if skipping, to avoid issues like https://its.cern.ch/jira/browse/ATR-28617
log
.
debug
(
"
Found %d CF sequences with filter name %s
"
,
len
(
foundCFSeq
),
filterName
)
if
not
foundCFSeq
:
sequenceFilter
=
buildFilter
(
filterName
,
filterInput
,
chainStep
.
isEmpty
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment