it would be more effective to test this first, then the pt cut and only after that check the Prob.
The probability computation is pretty heavy.
Also, put a check first that track_prob_max_ is between 0 and 1, else the cut makes no sense, but the computation wil still be done.

The cut track_prob_max should be named *min, not *max, because the requirement is too look at tracks with a prob above a value.
The value in the config file is 999, which means nothing will pass the cut.

the chi2 cut looks wrong, I'd expect tracks with chi2 above a cut to be skipped, not below.