This project is mirrored from https://github.com/mantidproject/mantid.git.
Pull mirroring updated .
- 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 16, 2020
-
-
Danny Hindson authored
Apply change to insert export macros into class definition using cmake GenerateExportHeader feature to 3 more projects: API, Crystal and CurveFitting Have replaced DllExport with the cmake macro except in these places: a) class templates - the definitions of class template member functions need to be in the same unit as the declaration so dllimport gives a compilation error in the client code (C2491 in VS) eg SingleValueParameter, SingleValueParameterParser b) headers which are in a project but aren't included by any .cpp units in the project eg IBackgroundFunction.h, ICatalogInfoService.h. In these cases I've removed the DLLExport attribute completely For the API target there were a couple of special cases\extras: API has some conditional use of the extern keyword to control instantiation of template classes. This has been inserted into the automatically created dllconfig.h using a cmake switch that allows some custom content to be appended to the end of the file. Few of the targets require this so I've added a boolean parameter to the wrapper function to handle this GENERATE_MANTID_EXPORT_HEADER I also had to add explicit include directories to PythonInterfaceCore where it imports an API target header (in the unit ExtractWorkspace.h) without having API as a dependency
-
- Mar 06, 2020
-
-
Harriet Brown authored
This commit replaces all header guards in LiveData with #pragma once
-
- Mar 05, 2020
-
-
David Fairbrother authored
Bumps the version of GTest to 1.10.0, removes the previous patching steps, which are no longer needed. Removes the extra handling which is provided in upstreams CMake, such as managing include directories
-
- Jan 31, 2020
-
-
Nick Draper authored
-
Nick Draper authored
-
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 13, 2020
-
-
Lamar Moore authored
-
Lamar Moore authored
-
Lamar Moore authored
-
Lamar Moore authored
-
- Jan 06, 2020
-
-
Dan Nixon authored
See KafkaEventStreamDecoder::~KafkaEventStreamDecoder for a full explanation of the issue and why the fix works. The same fix is not required in KafkaHistoStreamDecoder as it stores no intermediate state so the default destructor is restored.
-
Dan Nixon authored
The Kafka steam handles spectrum number, not detector ID.
-
- Dec 13, 2019
-
-
Lamar Moore authored
-
- Nov 20, 2019
-
-
Martyn Gigg authored
-
- Nov 19, 2019
-
-
Lamar Moore authored
-
Lamar Moore authored
-
- Nov 08, 2019
-
-
Nick Draper authored
re #27319
-
- Nov 06, 2019
- Nov 04, 2019
-
-
Moore authored
-
- Oct 28, 2019
-
-
Dan Nixon authored
Re #27061
-
- Oct 22, 2019
-
-
Gigg, Martyn Anthony authored
Use macOS over OSX to refer to system. Remove old OSX version workarounds Refs #26261
-
- Sep 23, 2019
-
-
Dan Nixon authored
Fixes incorrect logic that determines if the run ID can be converted to a run number. Before this fix all run IDs that could be run numbers would return -1 and all run IDs that were not valid run numbers would terminate.
-
Dan Nixon authored
Streamed data assumes spectra numbers start at zero.
-
Dan Nixon authored
Created incorrect boundaries when event count was low to moderate but most events fell on a single detector.
-
- Sep 17, 2019
-
-
Dan Nixon authored
When subscription to the topic that provides the spectrum to detector ID mapping fails or the message is otherwise not consumed generate a 1:1 mapping by loading the instrument before creating the buffers. This is a slightly hacky solution in time for V20 beam time, the spectrum to detector ID mapping may be later moved to the run start message, making this easier to handle. Fixes #26692
-
- Sep 10, 2019
-
-
Matthew D Jones authored
-
- Sep 07, 2019
-
-
Moore authored
-
- Sep 06, 2019
-
-
Moore authored
-
Matthew D Jones authored
-
- Sep 05, 2019
-
-
Moore authored
-
- Sep 04, 2019
-
-
Moore authored
-
- Aug 29, 2019
-
-
Dan Nixon authored
When subscription to the topic that provides the spectrum to detector ID mapping fails or the message is otherwise not consumed generate a 1:1 mapping by loading the instrument before creating the buffers. This is a slightly hacky solution in time for V20 beam time, the spectrum to detector ID mapping may be later moved to the run start message, making this easier to handle. Fixes #26692
-
- Aug 23, 2019
-
-
Moore authored
-