Setting MS order with setToCasaOrder?

Short version: don't use setToCasaOrder, it makes things even slower!

We discussed some time ago if we should apply setToCasaOrder just after importfitsidi in order to make the rest of the steps faster.

I have conducted some calibration starting from fits files and running

importfitsidi 
setToCasaOrder
fixvis
flag autocorrelations
Hanning smoothing
aoflagger + a-priori flags
split
etc...

The test was conducted on richards (12 CPU @ 3.50GHz, 64 GB of RAM). The data set if 184 GB in the original fits format.

Times to run different steps with setToCasaOrder: summary_test2_1

Times to run different steps with NO setToCasaOrder: summary_test2_3

Conclusions:

setToCasaOrder takes a long time. About 3h spent on setting the order of a 184 GB file.
Most of the following steps with unaveraged data take the same ammount of time.
Aoflagger seems to take much longer on ordered data. Making it more than 1h slower.
The split step (including averaging to 128chan/spw and 2sec) is also slower when applying setOrder.
The rest of the steps after averaging does not make a difference.
I see the same behaviour on unaveraged data.

I will update the code to take out that option. Maybe leave if it there as an option.

e-merlin / eMERLIN_CASA_pipeline