Do we have to include a description of the input fields, or is this not necessary since we have it as tooltips?

Bugfix UpdateInstrumentDefinitions.OnStartup and loading Facilities.xml

The logic in the check was switched to be negative `or` rather
than negative `and`. The two people I showed the change to thought
that the phrasing in this PR was clearer.

Engineering Diffraction GUI enable loading and plotting runs in the new GSAS tab

Updated instrument definition files for MAPS

Add bibtex file for users

FindPeaksMD calculate Goniometer rotation for CW

(default monitors values have changed)

Current parameters modified to correspond to new IDF

Add option to calculate the Goniometer rotation (around y-axis only) for a constant wavelength source. This will allow only one instrument definition to be held while peaks can be found for multiple sample rotations.

Add V20 IDFs

Add deprecation doxygen to WorkspaceFactory methods.

Add dependency on PythonInterface

Add ability to pickle table workspaces

Indirect - Fitting - ExtractQENSMembers Algorithm

This fixes #21360

Fix ErrorFormatter to workaround bug in Python 3.4

Force reset of googletest before applying patches

Refs #21648

GSASIIRefineFitPeaks output fitted peaks workspace

Sphinx training docs

Refs #21648

Fixes failing unit test for numpy >=1.14

In numpy 1.14 the precision of printing scalars changed. This rounds the number to the same as < 1.14 for the test.

Fix docstring directives for old sip definitions.

Remove Python.h include