GitLab

- If no saved data exists when loading, a valueerror is now raises. This
  catched that exception to work as expected.

Moritz Huebner: Made sampler.result a property and moved some of the stuff that happens in run_sampler in there.

Moritz Huebner: reintroduced kwargs property/setter, is probably better because that behaviour is getting inherited

Closes #68 by giving a simple interface to set the log-level (unless set
at the script level) and whether or not to use cached data.

- If the sampler kwargs are the same
- If the search parameter keys are the same

MISSING: check the priors. This requires a more detailed look into how
to compare our prior distribtions.

This demotes CC from a requirement to something optional. If
`ChainConsumer` is called when it is not installed, a warning message is
raised.

The samplers and prior access the parameters via
`likelihood.waveform_generator.parameters`. But, this is the only way
that the waveform_generator was accessed outside of the likelihood. We
simplify this by insisting that the Likelihood has the attribute
parameters (which is set, in this case, from the waveform_generator).

- Add attribute parameters to likelihood
- Remove all look-ups of waveform_generator outside of the likelihood.
  This means the waveform_generator is a likelihood-specific thing!

Functionally, this changes nothing, but it makes it clear that the
filled priors are the dictionary `priors`.

Previously, the dynesty kwarg for the number of live points was set to
be `npoints`, and so `npoints=10000` was passed to
`dynesty.NestedSampler`. This, however, is not the kwarg requried by
`NestedSampler`, but it instead should be `nlive`.  Unfortunately, this
error is silenced because the kwargs are just lost in dynesty.

- Fixes nlive kwarg
- Reduces default number from 10000 to 250 (as this was what was
  actually used before)
- Adds a verbose flag controlling the `run_nested` argument
  `print_progress`

- Set plot=False during tests
- Remove verbose=True from nestle calls

1) Remove the prior from the result object: we already save them as a
text file, so I don't think they need to be in the result. For now, I've
only commented them out with a message as there may be someone tempted
in the future to add it back in.

2) If the saving data does error, it now continues (without writing the
data) and prints a big error message.

Removes line which saves the raw dynesty output to file