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 27, 2020
  3. Mar 25, 2020
  4. Mar 20, 2020
  5. Mar 10, 2020
  6. Mar 09, 2020
  7. 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
  8. Mar 05, 2020
    • David Fairbrother's avatar
      Re #26260 Bump GTest to 1.10.0 · b6d965a4
      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
      b6d965a4
  9. Mar 03, 2020
  10. Mar 02, 2020
  11. Feb 27, 2020
  12. Feb 25, 2020
  13. 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
      Fix problems with output property lists · b9277f06
      Gemma Guest authored
      When assigning to a list of outputs when calling the algorithm in
      python, the outputs must be specified in the order they are declared,
      even if they are optional outputs like IvsLam. This means that if we
      want to specify the transmission workspace output we must first specify
      IvsLam even if debug is false. Some of the algorithms always output
      IvsLam if the name was given whereas others did not. They now always
      output it if the name is given.
      
      Note that this means you may now get an error if you don't supply enough
      arguments whereas previously it was ok. It is ok if you just specify the
      IvsQ output(s) but beyond that we do not know whether the output should
      be IvsLam or the transmission, so we require all of them, hence the
      error. This is better than it assigning an unexpected output so I think
      is ok, and is the only way I can think to do this.
      
      Re #27633
      b9277f06
    • 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
  14. Feb 20, 2020
  15. Feb 18, 2020
  16. Feb 17, 2020
  17. Feb 14, 2020
Loading