Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
PRConfig
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue 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
LHCb Data Packages
PRConfig
Commits
9703d272
Commit
9703d272
authored
1 year ago
by
Luke Grazette
Browse files
Options
Downloads
Patches
Plain Diff
Removed debugging print
parent
a6a77122
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!330
[RTADPA BW Tests] Introducing an Hlt1-bandwidth test via Moore_in_Allen
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
python/MooreTests/line-and-stream-rates.py
+0
-1
0 additions, 1 deletion
python/MooreTests/line-and-stream-rates.py
with
0 additions
and
1 deletion
python/MooreTests/line-and-stream-rates.py
+
0
−
1
View file @
9703d272
...
...
@@ -195,7 +195,6 @@ def processing_events_per_line_and_stream_hlt1(lines, inputfile):
# ToDo: remove this assumption if possible
# Assume that the event_size is independent w.r.t. which line fired.
# This 'might' be valid as no information per event is pruned out in hlt1.
print
(
events_file
)
raw
[
line
]
=
mdf_size
/
events_file
*
len
(
eventnumber_per_line
)
return
events_file
,
raw_size_all
,
dst_size_all
,
event_stats
,
exclusive
,
raw
,
dst
...
...
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