This reverts commit fef0db69.

This reverts commit b49ab9f8.

This reverts commit d186d95e.

- fixes nightly build failure

- also make sure ranking stat of candidate is shown.

- obtain from FAP curve.

- plot as markers, not a solid line
- use numpy array slicing to get x and y arrays instead of python loops.

- list of (x,y) pairs needs to be sorted by x co-ordinate.

- remove tag argument from plot_likelihood_ratio_ccdf()
- change title:  this is not the CCDF, this is FAP vs. ranking stat
- edit y axis label to be more explicit about what is plotted.

- from "NONE-GSTLAL..." to "COMBINED-GSTLAL..." for consistency with PDF plots.

- attemps a fixed number of retries on upload failure, waiting a log-normal
  distributed delay betewen each
- refs #2456

gstlal_ll_inspiral_create_prior_diststats: create a zero lag ranking file and cache for the low latency pipeline

- (snr, \chi^2) numerators are computed analytically.  previously, changes
  to the KDE used to estimate the denominator PDF from sample histograms
  could change sensitivity measurements simply because of the effects those
  changes were having on the numerator signal model.  this patch removes
  that confusion.
- because the limited set of discrete prefactors used for constructing the
  numerator creates a stair-step effect, some amount of smoothing is
  desired in the numerator regardless.  this is smoothing, not density
  estimation, they are distinct from one another although the same code has
  been used to accomplish both in the past.  this patch moves that
  smoothing to where the source of the banding is in the code to
  disentangle it from the background density estimation.  if the prefactor
  banding is adjusted, that smoothing can be adjusted as well without
  entangling it with the denominator's kernel design.
- refs #2339

- refs #2429

- replace
	if blah:
		...

  with
  	if not blah:
		return
	...

- a histogram of likelihood ratios assigned to zero-lag candidates is
  required to implement the low-significance extinction model.  this patch
  reorganizes the source and sink of that information to be a separate file
  rather than piggy backing the data on the candidate parameter PDF file
  supplied to the trigger generator, e.g., during online running.

- immediately, this allows the statistics uploaded to gracedb along with
  each candidate to contain the actual ranking statistic PDF data used to
  rank the event, whereas prior to this patch it contains a mix of the
  candidate parameter PDFs and whatever was in the zero-lag histogram data
  supplied on input.  going forward, keeping distinct, unrelated, pieces of
  information in distinct places with different names that get supplied to
  programs using distinct command line options will prevent confusion over
  what is being stored where.

- refs #2429

- when doing online injection runs.
- online injection runs use an externally supplied coinc params
  distributions object, and the way that feature had been put in led to
  .finish() being invoked on such an object twice.  only need to do it
  once, on whichever will actually be used for computing ranking
  statistics.  this patch reorders a few statements and comments to remove
  the second .finish()

- this is only required for online running, and is actually forbidden for offline running.

- each time through the loop this script causes a relatively small number of ranking statistic samples to be generated, with the original intention being that over time the total number of samples would accumulate to something large.  this script discards the samples from the previous iteration, however, and starts over again from scratch each time.
- this patch modifies the script to include the output from the previous iteration in this iteration so that the ranking statistic histogram gathers additional samples over time.
- surprisingly the results seemed to be OK in the past, so it's possible that we don't need to do this.  in that case, this is a trivial stand-alone patch that can be easily reverted at a later time if desired.

- allows plots to be hacked to show the results had a ranking statistic threshold been imposed.

- move .finish() invocations into load_distributions() function

- because that's a more convenient indication of the contribution of these parameters to the ranking statistic than either the raw value or log-base-10 of the value.

- for consistency with other plots.

- in summary pages.
- refs #2427

CIT

running