Seismic

What's Changed
* SeisMIC does now take location codes into account. Unfortunately, this results in an incompatibility with the old h5-databases. Hence, SeisMIC 0.6.5 does not read or write to old databases.


**Full Changelog**: https://github.com/PeterMakus/SeisMIC/compare/v0.5.23-beta...v0.6.5-beta

This release introduces a number of minor features:

What's Changed
- A bug in the conversion of geographic to local coordinate system was fixed that caused inaccuracies in regions far away from the meridian and the equator
- Component option can now be defined in `params.yaml`
- Allow computing the posterior covariance for the LLQ spatial inversion
- Introduced method to align newly incoming *dv/v* estimates to an existing *dv/v* grid
- other minor rutines and functionalities where changed




**Full Changelog**: https://github.com/PeterMakus/SeisMIC/compare/v0.5.3-beta...v0.5.23-beta

This is SeisMIC's release associated with the paper preprint.

Since the last version, a whole lot of chances have happened. Some of them are listed here:

- Spatial Inversion of seismic velocity changes to create a seismic velocity change map
- computing spectrograms directly from the raw data
- computing the waveform coherence
- Performance improvements for single and multi-core computations.
- a whole lot of minor changes (refer to the list of commits for details)

The first official SeisMIC release :partying_face:

This version is fairly well-tested and should work. However, it does not contain all latest features.

With this version you will be able to:

- download continuous seismic data from FDSN providers or use data you have locally available
- Compute cross-, self-, or autocorrelations
- Access these correlations from hdf5 containers
- Compute seismic velocity changes from these correlations
- Plotting tools
- A bunch of pre and postprocessing functions

Most notably, you will not be able to compute spatial dv/v solutions. This feature is currently only available on the ``dev`` branch.

If you should experience bugs, please create an issue here on GitHub.