Skip to content

Conversation

@shahor02
Copy link
Collaborator

@shahor02 shahor02 commented Dec 2, 2024

--run-time-span-file <text file with run range_min range_max entries>

This option allows to push to DPL only those TFs which overlap with the <runnumber> <range-min> <range-max> (separators can be any whitespace, comma or semicolon) records provided via text file (assuming that there are some entries for a given run, otherwise the option is ignored).
Multiple ranges per run and multiple runs can be mentioned in a single input file. The range limits can be indicated either as a UNIX timestamp in ms or as an orbit number (in the fill the run belongs to).

In case an option

--invert-irframe-selection

is provided, the selections above are inverted: TFs matching some of the provided ranges will be discarded, while the rest will be pushed to the DPL

At the end of the processing the ctf-writer will create a local file ctf_read_ntf.txt containing only the number of TFs pushed to the DPL.
If no TF passes the selections above, this file will contain 0.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2024

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

@shahor02
Copy link
Collaborator Author

shahor02 commented Dec 2, 2024

@chiarazampolli

New option
--run-time-span-file <text file with run range_min range_max entries>
allows to push to DPL only those TFs which overlap with the
<runnumber> <range-min> <range-max>
(separators can be any whitespace, comma or semicolon) records provided
via text file (assuming that there are some entries for a given run,
otherwise the option is ignored).

Multiple ranges per run and multiple runs can be mentioned in a single
input file. The range limits can be indicated either as a UNIX
timestamp in ms or as an orbit number (in the fill the run belongs to).

In case an option --invert-irframe-selection is provided, the selections above are inverted:
TFs matching some of the provided ranges will be discarded, while the rest will be pushed to the DPL

At the end of the processing the ctf-writer will create a local file ctf_read_ntf.txt containing only
the number of TFs pushed to the DPL.
In case no TF passed the selections above, this file will contain 0.
@chiarazampolli
Copy link
Collaborator

Thanks!

@chiarazampolli
Copy link
Collaborator

Hello @shahor02 ,

Can one add a tab separation? This is the easiest to export in csv format (even if also the others work).

Chiara

@shahor02
Copy link
Collaborator Author

shahor02 commented Dec 3, 2024

Hi, as the commit says, the separator can be whitespace (tab, space), comma or ;

@shahor02 shahor02 merged commit 4bffbfa into AliceO2Group:dev Dec 3, 2024
12 checks passed
@shahor02 shahor02 deleted the pr_ctfselrange branch December 3, 2024 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants