Release candidate v8.0.0-rc3

Release candidate for new major release v8.0.0, do not use yet. Attempt to update smurf-pcie version used by server to latest version v3.0.2 failed ; trying new smurf-pcie version v2.0.0.1 which is based on v2.0.0 but slightly modified. Changes include fixing submodule urls.

Full Changelog: v8.0.0-rc2...v8.0.0-rc3

Release candidate v8.0.0-rc2

Release candidate for new major release v8.0.0, do not use yet. Attempting update of smurf-pcie version used by server to latest version v3.0.2. Previous versions were using older version v2.0.0.

We flew too close to the sun - this doesn't work for subtle reasons, likely related to differences in surf firmware submodule between latest smurf-pcie version and current SMuRF release versions. See https://jira.slac.stanford.edu/projects/ESCRYODET/issues/ESCRYODET-941 for details. Will revert.

Full Changelog: v8.0.0-rc1...v8.0.0-rc2

v8.0.0-rc1

Updates rogue version in dockers to v4.11.11 to allow use of latest PCIe card software driver version v5.19.1 (in slaclab/rogue#970).
Is not compatible with previously used version of PCIe card software driver v5.7.0 (32-bit versus 64-bit address API in the driver).
Release candidate for new v8.0.0, do not use yet. Incrementing major version number because of backwards incompatibility with previously used driver version v5.7.0.

Full Changelog: v7.4.0...v8.0.0-rc1

v7.4.0

Tested on TKID AC chip in SLAC DR, see tkid_v7_4_0_release_testing_20230711.ipynb for verification.

Known issues

Nothing major (besides known issues...yet).

What's Changed

• Enable hardware detection for systems running a single TKID AMC in bay 0 by @swh76 in #782
• Add TKID fw & zip file into releases, enhance server hardware detect to choose which fw & zip file to use based on which AMCs are installed in the SMuRF carrier. by @swh76 in #783

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• cryo-det-kid firmware release: v2.0.0
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.5...v7.4.0

v7.3.5

Needs end-to-end bench and cryo testing.

Known issues

Nothing major (besides known issues...yet).

What's Changed

• ADC->DAC in y-axis label of read_dac_data plots. by @swh76 in #779
• Fix for overlapping title in plots produced by check_full_band_resp by @swh76 in #778
• Adding timeout as an option to the underlying epics.PV.get call with 5 sec as default by @swh76 in #781

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.4...v7.3.5

v7.3.4

Known issues

• #780 - PV gets timing out / saturating max # of tries in releases > v7.1.0 due to difference between epics.caget and epics.PV.get default timeout.

What's Changed

• Dockerfile fix so core pysmurf instance can figure out its version tag. by @swh76 in #777

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.3...v7.3.4

v7.3.3

BROKEN! Core pysmurf instance unable to determine its version!

Known issues

Nothing major (besides known issues...yet).

What's Changed

• Minor bug fixes. by @swh76 in #774
• Drops pydm from v1.18.2 to 1.17.0. by @swh76 in #775
• Attempted fix for pysmurf.__version__. by @swh76 in #776

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.2...v7.3.3

v7.3.2

BROKEN! Server reports bad data for critical low level routines like read_adc_data and find_freqs

Known issues

#772 - v7.3.2 server reporting incorrect data for critical routines like read_adc_data and find_freqs.
#773 - Core code unable to ascertain pysmurf software version.

What's Changed

• Update to new smurf-rogue-docker release R2.9.1 which fixes server gui crash. by @swh76 in #769
• Fixing deprecated numpy.int call after numpy upgrade. by @swh76 in #771

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.1...v7.3.2

v7.3.1

BROKEN! Server gui crashes & some function calls broken due to deprecation of numpy.int in upgraded client docker - do not use!

Known issues

• #768 Server gui crashes
• #770 Some function calls like read_adc_data and read_dac_data crashing because np.int is no longer available in the newer numpy version now used by dockers after upgrading to Ubuntu 20.04.

What's Changed

• Reverting smurf-pcie version from v2.3.0 back to v2.0.0 in #767

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.3.0...v7.3.1

v7.3.0

BROKEN! Server crashes - do not use!

Known Issues

• #766 - Server crashes!

What's Changed

• Fix bug causing plot_tune_summary to crash if eta_scan=True and there are any unassigned channels in freq_resp dict. by @swh76 in #758
• Upgrade Ubuntu in the base and rogue dockers from version 18.04 to 20.04. by @swh76 in #765
• Rogue defaults fix for RTM precision slow DAC configuration to prevent railing fullscale negative for ~1 sec on configure. by @swh76 in #763
• Add set/get for MaxFileSize to allow splitting long streaming acquisitions over multiple files based on file size. by @swh76 in #760

The stable server Docker image uses the following firmware and config

• cryo-det firmware release: v1.1.1
• smurf_cfg release: v2.0.0

Does this PR break any interface?

• Yes
• No

Full Changelog: v7.2.0...v7.3.0