This project is mirrored from https://github.com/mantidproject/mantid.git.
Pull mirroring updated .
- Apr 02, 2020
-
-
Peterson, Peter authored
This caused an issue with nested imports on Qt < 5.9
-
- Mar 25, 2020
-
-
David Fairbrother authored
Runs clang-tidy pass by ref across the codebase to fix-up various warnings we are seeing in cppcheck
-
- Mar 20, 2020
-
-
Nick Draper authored
Also updated class_maker.py
-
- Mar 10, 2020
-
-
Giovanni Di Siena authored
-
Harriet Brown authored
This commit replaces all header guards in qt/Widgets with #pragma once.
-
- Mar 06, 2020
-
-
David Fairbrother authored
Fixes the progress arrow which previously only pointed at the first line, irrespective of selection. Additionally removes a method which is completely unused in the code-base, but looks like it would do a similar thing as it's misleading. A struct is used in case we need to add additional fields, and for the extra readability when we dereference the map iterator. This avoids a iter->value.at<0> in favour of having named fields of a struct.
-
- Mar 03, 2020
-
-
Nick Draper authored
in a derived class re #28185
-
- Feb 27, 2020
-
-
Nick Draper authored
-
Nick Draper authored
-
- Feb 21, 2020
-
-
Martyn Gigg authored
This implementation is based on the implementation in MantidPlot. A C++-based executor has been added that can execute Python code with the option of installing a trace function to update a progress marker on a given editor window. The old implementation attempted to chunk up the script into the smallest executable blocks and mark each of these as when they were executed. There were 2 issues: - the chunking of the scripts was error prone as it actually requires a good knowledge of how Python internally handles indentation etc. It was fairly easy to break and future internal updates to Python would have required unknown changes. - the progress reporting resolution was far poorer than MantidPlot as the actual line being executed was not reported but inferred by what block was being executed giving a false sense of progress through a script.
-
Gemma Guest authored
Changes related to this PR have caused test failures in the data processor UI because they use one of the changed reflectometry algorithms. Reflectometry no longer uses the data process, so this is somewhat obsolete. In order to maintain working tests I've added an option to specify the version of the algorithm to create in the ProcessingAlgorithm so that we can maintain the previous behaviour and previous tests. Re #27633
-
- Feb 20, 2020
-
-
Alice Russell authored
-
Alice Russell authored
This allows constraints to be empty so that if one is removed or if only one constraints is required it handles it correctly
-
- Feb 18, 2020
-
-
Nick Draper authored
-
Nick Draper authored
-
- Feb 17, 2020
-
-
Alice Russell authored
-
Alice Russell authored
When a documentation page does not exist for a function it will now display the function index page rather than page not found.
-
Alice Russell authored
-
- Feb 12, 2020
-
-
Alice Russell authored
-Change behaviour of double click so error does not appear if clicking on the category -SelectFunctionDialog changed to be modal
-
Alice Russell authored
If the user enters an incorrect function into the search bar it will now give an within the dialog and keep the dialog open
-
- Feb 11, 2020
-
-
Stephen authored
Fitting now conforms to user fit range TF asymmetry fits work in single fit mode The list of fit workspaces now preserves order
-
Stephen authored
-
Stephen authored
The fitting tab was keeping a reference to two function browsers, which had to kept up-to-date with each-other. This issue has been addressed by introducing a single function browser.
-
Nick Draper authored
-
- Feb 10, 2020
-
-
Alice Russell authored
-
Matthew Andrew authored
-
Matthew Andrew authored
-
Matthew Andrew authored
-
Matthew Andrew authored
-
Matthew Andrew authored
-
Matthew Andrew authored
-
Matthew Andrew authored
This updates the handling of which resolution spectra to use for each spectra in the fit. This needed updating because for multiple files it was using the convolution for the first file for all files and because how QENSFitSequential and QENSFitSimultaneous handle convolutions is different. The sequential version requires a single workspace which contains all of the resolutions whereas the simultaneous version requires the resolutions to be encoded into the FitFunction.
-
Matthew Andrew authored
-
Matthew Andrew authored
-
- Feb 03, 2020
-
-
Conor Finn authored
-
- Jan 31, 2020
-
-
Nick Draper authored
-
Nick Draper authored
Previously an algorithm only appeared when a progress message came in re #27077
-
Nick Draper authored
This was due to: 1. Too long a default UpdateEvery default 2. Too infrequest progress updates from MonitorLiveData 3. The Algorithm Details box not adding an algorithm until it sends a progress update 4. The StartLiveData custom Dialog not showing the default for UpdateEvery Fixes: 1. Decreased the default UpdateEvery from 60 to 30 seconds 2. Change the default timeout for FakeISISHistongramDAE from 30 to 60s 3. improved the progress logging for MonitorLivedata to update more frequently with an idle counter as well. 4. Changed the tie function used in custom algorithm dialogs to set the placeholder text for line edits 5. Changed the log level for user cancelling of algorithms from Error to warning so it does not trigger the notification service 6. Changed the log message for user cancellation from Terminated to cancelled to reduce confusion re #27077
-
- Jan 29, 2020
-
-
Alice Russell authored
-
Alice Russell authored
The FitPropertyBroswer originally made it's own selector dialog, this commit changes it to use the SelectFunctionDialog that already exists
-