SlicingAlgorithm holds a reference to the original MDEventWorkspace
and keeps the file handle to cncs.nxs open for too long in a release
build such that a later SaveMD call cannot overwrite the same file.

This Commit gives users the option of setting the Lorth filter on polaris PDF. Previously this was hard coded to true but will now be turned off by default.

Added missing include that was working on Windows due to precompiled header
Make linking to lib3mf conditional for DataHandlingTest as well as DataHandling
Create unit tests for 3mf file import (Mantid3MFFileIOTest)
Remove tabs from Pearl.xml file
Make 3mf import work with multiple levels of Components in .3mf file
Enhance material handling in Mantid3MFFileIO to use MaterialXMLParser
Add support for 3mf format to two more algorithms: LoadSampleEnvironment and
SaveSampleEnvironmentAndShape now support 3mf format files
Update Windows 3rd party build to use to version with lib3mf

This Commit fixes failing system tests in ISIS powder polaris.

re: #28415

this commit adds system tests covering the new rebin options in the polaris create total scattering script.

re: #28415

Accidentally removed inheritance of systemtesting.MantidSystemTest when
removing with_metaclass and add_metaclass. Put them back.

Removes all of the from __future__ imports that open and close the
brackets on the same line. This is most of them.

New function and unit test to read the goniometer angles from a run log and then refine the Goniometer angle and axes and make exported UBs consistent

Add feature where an externally generated attenuation profile can be loaded into
the material definition from a .DAT text file. This will override the normal
exp(-alpha*thickness) calculation of the attenuation. The new feature was requested
as part of the absorption calculation for the Pearl instrument where some parts
of the environment are crystalline

Found the lookup\interpolation on the loaded profile was slowing down the absorption
Monte Carlo calculation.
So improved performance of Kernel::Interpolation. Changed it to use vector of pairs
instead of two separate vectors to reduce amount of navigation around vectors

Considered adding feature into AttenuationProfile where I add any interpolated points
into the override attenuation profile to prevent interpolation next iteration of
Monte Carlo simulation. However wasn't convinced this was going to be thread-safe
during the parallel part of the absorption calculation - may revisit this. While doing
this investigation I fixed the following issues with the function Interpolation::AddPoint:

a) it doesn't add the same point twice
b) it reuses the lower_bound function rather than stepping through the vector sequentially

I removed the exception from findIndexOfNextLargerValue because the end()
iterator is a valid result if the x value supplied equals the last x value
already in the vector. Could have left check in for begin() but didn't seem
much point

Finally - the interpolation outside the range is not v good. The data at the extremes
is noisy so we end up extrapolating based on random gradient in extreme 2 points. Need
to either fit or use more points to determine gradient

Also updated class_maker.py

Attempts to flush out the cause for the failing nightly clean build on
Windows. This is periodically failing on both the release / master clean
builds without any reason why.

Fixes all flake8 3.7.9 warnings as part of the Python 2->3 transition.

Because that seems to be the convention for parameter capitalization.

On a few remaining occurences, the default parameter
(convertToTOF=false) was not the expected one for the test to pass.

This commit replaces all header guards in testing with #pragma once.

subprocess.communicate returns a bytes object but File.write requires a str object