You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be enough, and less confusing, to just specify the number
of timeframes to be simulated (as well as potentially the timeframe length in orbits).
So we now do the setting for NSIGEVENTS internally (the o2dpg_sim_workflow script
still needs it) but keep the option to provide it for expert studies.
Also taking away the need to provide CYCLE (which is mostly 0 in any case).
# The number of signal events can be given, but should be useful only in
149
+
# certain expert modes. In the default case, the final event number is determined by the timeframe length.
150
+
if [ -z"NSIGEVENTS" ];then
151
+
NSIGEVENTS=10000 # this is just some big number; In the simulation the event number is the minimum of this number and what fits into a single timeframe
152
+
# based on the interaction rate. The number is a reasonable upper limit related to ~5696 collisions that fit into 32 LHC orbits at 2MHz interaction rate.
153
+
fi
154
+
155
+
if [ -z"${CYCLE}" ];then
156
+
echo_info "No CYCLE number given ... defaulting to 0"
157
+
CYCLE=0
158
+
fi
150
159
151
160
# this generates an exact reproducer script for this job
0 commit comments