Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eventsToProcess #523

Open
jgalan opened this issue Jun 3, 2024 · 1 comment
Open

eventsToProcess #523

jgalan opened this issue Jun 3, 2024 · 1 comment
Assignees
Labels
good-to-know Something crucial you think should be shared with the community

Comments

@jgalan
Copy link
Member

jgalan commented Jun 3, 2024

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.

@jgalan jgalan added the good-to-know Something crucial you think should be shared with the community label Jun 3, 2024
@lobis
Copy link
Member

lobis commented Jun 4, 2024

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.

@lobis lobis assigned restforphysics and unassigned lobis Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-to-know Something crucial you think should be shared with the community
Projects
None yet
Development

No branches or pull requests

3 participants