Skip to content

Commit

Permalink
Set default firstOrbit to 256
Browse files Browse the repository at this point in the history
just a preventive measure in case someone is using --early-orbits
(avoid to get negative).
In the worst case we skip few timeframes ... and in any case not
a relevant change for anchored MC.
  • Loading branch information
sawenzel committed Nov 1, 2024
1 parent 370602d commit 91da4e6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion MC/bin/o2dpg_sim_workflow.py
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@
parser.add_argument('--no-tpc-digitchunking', action='store_true', help=argparse.SUPPRESS)
parser.add_argument('--no-strangeness-tracking', action='store_true', default=False, help="Disable strangeness tracking")
parser.add_argument('--combine-tpc-clusterization', action='store_true', help=argparse.SUPPRESS) #<--- useful for small productions (pp, low interaction rate, small number of events)
parser.add_argument('--first-orbit', default=0, type=int, help=argparse.SUPPRESS) # to set the first orbit number of the run for HBFUtils (only used when anchoring)
parser.add_argument('--first-orbit', default=256, type=int, help=argparse.SUPPRESS) # to set the first orbit number of the run for HBFUtils (only used when anchoring); default 256 for convenience to allow for some orbits-early
# (consider doing this rather in O2 digitization code directly)
parser.add_argument('--orbits-early', default=0, type=float, help=argparse.SUPPRESS) # number of orbits to start simulating earlier
# to reduce start of timeframe effects in MC --> affects collision context
Expand Down

0 comments on commit 91da4e6

Please sign in to comment.