idf_screen allows the user to alter the screening performed by the pipeline.
Usage: idf_screen [-h] [-v level] input_idf_file output_idf_file timeflag value Arguments : timeflag : USER/JITR/OPUS/BRST/HV/SAA/LIMB/DAY value : GOOD/BAD/EITHER Options: -h: this help message -v: verbosity level (=1; 0 is silent)
The following example selects only the night-time events:
idf_screen M10101010011attagfidf.fit M10101010011a_night_ttagfidf.fit DAY GOOD
(In this case, GOOD = NIGHT and BAD = DAY.)
In the next example, the timeline and events BURST timeflags are set to zero:
idf_screen M10101010011attagfidf.fit M10101010011a_ignorebursts_ttagfidf.fit BRST EITHER
Finally, the timeline and events list JITR timeflags are inverted:
idf_screen M10101010011attagfidf.fit M10101010011a_jitter_ttagfidf.fit JITR BAD
Thus the extraction routine will think that the times when the jitter is good are the times when the jitter is bad. It is tricked into extracting only the events for which the jitter is bad (and the other conditions are satisfied).
Note that using one of the timeflags other than DAY with the value GOOD doesn't change the screening parameters. In that case, idf_screen doesn't generate the output file.
idf_screen does not update the GTIs table.