Add reordering for aoflagger (RAP-129)

In order to avoid a huge main memory usage of the aoflagger step, the user should be enabled to make use of the indirect-read (aka reorder) mode of aoflagger. See RAP-129

docs/source/calibrator.rst

@@ -278,8 +278,7 @@ A comprehensive explanation of the baseline selection syntax can be found `here`
 
 - ``max_dppp_threads``: number of threads per process for DP3 (default: 10)
 - ``memoryperc``: maximum of memory used for aoflagger in raw_flagging mode in percent (default: 20)
-- ``min_length``: minimum amount of subbands to concatenate in frequency necessary to perform the wide-band flagging in the RAM. It data is too big aoflag will use indirect-read (default: 50)
-- ``overhead``: only use this fraction of the available memory for deriving the amount of data to be concatenated (default: 0.8)
+- ``aoflag_reorder``: make aoflagger reorder the measurement set before running the detection. This prevents that aoflagger will use its memory reading mode, which is faster but uses more memory (see the `AOFlagger manual`_`)
 
 **Parameters you may want to adjust**
 
@@ -297,3 +296,4 @@ A comprehensive explanation of the baseline selection syntax can be found `here`
 
 .. _here: https://www.astron.nl/lofarwiki/doku.php?id=public:user_software:documentation:ndppp#description_of_baseline_selection_parameters
 .. _AOFlagger: https://gitlab.com/aroffringa/aoflagger.git
+.. _AOFlagger manual: https://aoflagger.readthedocs.io/en/latest/using_aoflagger.html
\ No newline at end of file