Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/mantidproject/mantid.git. Pull mirroring updated .
  1. Apr 02, 2020
  2. Mar 25, 2020
  3. Mar 20, 2020
  4. Mar 10, 2020
  5. Mar 06, 2020
    • David Fairbrother's avatar
      Re #28266 Fix progress arrow for Workbench · 2d147299
      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.
      2d147299
  6. Mar 03, 2020
  7. Feb 27, 2020
  8. Feb 21, 2020
    • Martyn Gigg's avatar
      Replace block-style progress reporter with C-api based one · f35671a7
      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.
      f35671a7
    • Gemma Guest's avatar
      Allow ProcessingAlgorithm to use old version of algorithms · c8dd50d9
      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
      c8dd50d9
  9. Feb 20, 2020
  10. Feb 18, 2020
  11. Feb 17, 2020
  12. Feb 12, 2020
  13. Feb 11, 2020
  14. Feb 10, 2020
  15. Feb 03, 2020
  16. Jan 31, 2020
    • Nick Draper's avatar
      clang formatting for this pr · d4dc5ed9
      Nick Draper authored
      d4dc5ed9
    • Nick Draper's avatar
      Algorithm Progress details fills with all algorithms on creation · 570c00d9
      Nick Draper authored
      Previously an algorithm only appeared when a progress message came in
      re #27077
      570c00d9
    • Nick Draper's avatar
      Reslove MonitorData not showing in the workbench algorithm details box · 55ad2798
      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
      55ad2798
  17. Jan 29, 2020
Loading