This plot visualizes the monthly statistics of executed detector ABs
('det.ABs'): <br>
- <b>number of all successfully processed ABs </b><br>
(before XXLight: successful CAL+SCI; with XXLight: successful CAL only), <br>
- <b>total execution time for ABs</b> in hours
(pipeline processing), <br>
- <b>total QC report execution time</b> in hours.</font><p><font size="2">

The significant drop in execution times in 2013-04 is caused by the migration to the muc machines,
with a significant gain in compute performance.</font><p><font size="2">

If applicable we have added metrics for IDPs. The initial peak refers to the
(re)processing of the entire historical batch.</font><p><font size="2">

The det.AB number refers to <b>jobs per detector</b> and is higher by a factor MEF_FACTOR
than the actual number of ABs as counted in the QC system and displayed in the
<a href=trend_report_AB_certif_ALL_HC.html>AB certification</a> plot.
For reference, MEF_FACTOR=4 for
CRIRES and HAWKI; 16 for VIRCAM; 32 for OCAM; 3 for KMOS; 24 for MUSE. This number measures 
the compute workload. </font><p><font size="2">

The numbers for AB_texec and QC_texec are the sum of execution times for all
processed ABs (including the failed ones), without further correction for
MEF_FACTOR. </font><p><font size="2">

<b>Note:</b> The latest data point in the current plot usually refers to a month which is not yet finished.
Its value will therefore continue to increase until a new last month starts.