PostProccess are designed to complement PostFilters. While PostProcesses
operate on the entire resultset at once, with PostFilters, each PostFilter
is called for each result in the resultset. PostProcesses can operate on the entire
querying.postprocesses.controls : A comma separated list of control to PostProcess
class mappings. Mappings are separated by ":". eg querying.postprocess.controls=qe:QueryExpansion
querying.postprocesses.order : The order postproceses should be run in
'''NB:''' Initialisation and running of post processes is carried out by the Manager.
Methods inherited from interface org.terrier.querying.Process