**Release date:** 2019-12-29
**Features**
* **binary system radial velocities curves modeling**
- radial velocity curves based on movement of center of mass computed upon astro-community quantities (:math:`q`, :math:`asini`)
* **capability to compute lightcurves on several processor's cores (multiprocessing)**
- split supplied phases to `N` smaller batches (N is equal to desired processes but up to number of available cores) and computed all at once
* **fitting parameters of binary system**
- light curve fitting using ``Markov Chain Monte Carlo`` (capability to fit using standard physical parameters :math:`M_1`, :math:`M_2` or parameters used by community :math:`q` (mass ratio) and :math:`a` (semi major axis))
- light curve fitting using ``non-linear least squares`` method (capability to fit using standard physica; parameters :math:`M_1`, :math:`M_2` or parameters used by community :math:`q` (mass ratio) and :math:`a` (semi major axis))
- radial velocity fitting based on ``Markov Chain Monte Carlo`` method (standard physical parameters, :math:`M_1`, :math:`M_2`, :math:`e`, :math:`i`, :math:`{\omega}`, :math:`{\gamma}`
- radial velocity fitting based on ``non-linear least squares`` method (standard physical parameters, :math:`M_1`, :math:`M_2`, :math:`e`, :math:`i`, :math:`{\omega}`, :math:`{\gamma}`
* **more specific errors raised**
- created several different type of errors (see ``elisa.base.errors`` for more information)
**Fixes**
- `elisa.observer.Observer.observe.lc` and `elisa.observer.Observer.observe.rv` will not raise an error in case
when parameter `phases` is `numpy.array` type
- adaptive discretization of binaries do not allow to change distretization factor out of prescribed boundaries
(it used to lead to small amount of surface points and then triangulation crashed)
- app does not crash on `phase_interval_reduce` in observer during light curve computation
if BinarySystem is not used from direct import of `BinarySystem`
- const PI multiplicator removed from output flux (still require investigation)
- app does not crash if `bolometric` passband is used
- np.int32/64 and np.float32/64 are considered as valid values on binary system initialization