Mantid 4.0 Workbench

[Hamish_C]

Hi @AnthonyLim.

I tested the same data reduction using MantidPlot and MantidWorkbench (same version, 4.1) via the Indirect Data Reduction window.

If you want to try it, I was using TOSCA run numbers “23081-23089” and summing the files. All other data reduction settings left as default. On MantidPlot it took maybe 5-8 seconds, on Workbench I would say it took at least 5x as long. Clicking save on both gave me the same sized “.dat”, at 125 kb.

Hopefuly I’ve not misunderstood anything and that is helpful!

[martyngigg]

Hi Hamish,

I just wanted to let you know that fixes for the points 2, 3 & 5 are now in the nightly build of mantid available from the download page. Thanks again for providing the feedback.

Martyn

[creigelde]

@jameslord

Spurious “Syntax error: unexpected indent” with scripts which work OK in MantidPlot. The offending line is some way into the script and is not the first at that indent level. For example my “AnalyseThresholdScans9.py” which is on the Script Repository under Muon if you want a look. It has tab indents. If I run “Tabs to Spaces” it does run OK. (It already had some but perhaps not all required import statements at the top)

As the error message indicates, you have an unexpected indent error. This error occurs when a statement is unnecessarily indented or its indentation does not match the indentation of former statements in the same block. Python not only insists on indentation, it insists on consistent indentation . You are free to choose the number of spaces of indentation to use, but you then need to stick with it. If you indent one line by 4 spaces, but then indent the next by 2 (or 5, or 10, or …), you’ll get this error. Whenever you have a situation with code inside of a statement, that inside code must be indented, and must be indented consistently. It is used by the interpreter to know how to delimit blocks of instructions.