v1.2.5

Repair mistake of failing to change soversion before tagging with v1.2.4. soversion and tag number are again consistent.

v1.2.4: Python 3 support

Some minor changes to support builds of under python 3

v1.2.3: vyssim data

Added new mode for vyssim to generate visibilities as random normal deviates. The previous operating mode, in which visibilities contain encoded metadata, continues to exist as an option, but as the encoded value mode is mainly useful for debugging, the default mode is to generate the random values.

v1.2.2

Restore Consumer.test_end() to avoid a major version update (but continue not to call it from Consumer methods). Use of this method will produce a DeprecationWarning.

v1.2.1

Remove Consumer.test_end()

v1.2.0

Rename vys_spectrum_max_buffer_size() to vys_max_spectrum_buffer_size() for consistency with naming in the vysmaw configuration file.

v1.1.1

Fixes externally callable versions of the buffer size functions introduced in v1.1.0.

v1.1.0

Adds functions for use by applications to compute the buffer size needed to receive spectra given a number of channels, number of pulsar phase bins, and, optionally, the stride between the spectra in adjacent phase bins.

v1.0.1

Updates a value in vysmaw.pxd that was missed in changes leading to v1.0.0.

Initial release of libvysmaw

This marks the initial release of libvysmaw, and the start of disciplined (we hope) version numbering. In addition to providing certain library API guarantees, version numbering will promote compatibility of vys producers and consumers by being tied to versions of the vys protocol. In fact, libvysmaw1.0.0 includes an update to the vys protocol relative to other recent libvysmaw development versions, which under strict versioning would necessitate a change to the major version number of libvysmaw, making this a good point to start doing that.