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
I would like to control the number of input events to be processed, this was the default behavior before when setting the value of eventsToProcess. Instead, now, eventsToProcess will control the number of events on the output file.
It is still possible to achieve the previous behavior? I.e. launch 1000 events processing and get the number of events that were accepted (between those 1000) in the output.
The text was updated successfully, but these errors were encountered:
Looking at the code it appears it's been this way for a long time now (I wasn't the one who modified it).
I don't think it possible to set the number of events to be processed (which I also think the current name of this option is misleading) but it shouldn't be too hard to achieve.
I think "events to process" should work as you describe: the number of input file events to be processed. To maintain consistency with restG4 this should use the -n flag.
Another option, "events in output file" should do what the events to process does currently, stop when a given number of events in the output file is reached. This should use the -e option as it does right now.
I would like to control the number of input events to be processed, this was the default behavior before when setting the value of
eventsToProcess
. Instead, now,eventsToProcess
will control the number of events on the output file.It is still possible to achieve the previous behavior? I.e. launch 1000 events processing and get the number of events that were accepted (between those 1000) in the output.
The text was updated successfully, but these errors were encountered: