v1.5.8

This is a minor release that contains one small improvement.

ENHANCEMENTS:

• solve.includeTravelTimeResiduals option is replaced by solver.absoluteLocationConstraint. If your configuration uses solve.includeTravelTimeResiduals, please replace it with the new solver.absoluteLocationConstraint one.

solver.absoluteLocationConstraint allows to include additional equations in the double-difference system (one equation for each event phase) that constrain the absolute travel time residuals (RMS) of the phases of the events being relocated. This forces the solver to find a solution that tries to improve the relative locations while positioning the cluster(s) in the absolute location that minimizes the overall RMS. However this is a trade-off and giving too much weight to the absolute location constraint prevents the solver from improving the relative locations.