Peter Willendrup

It seems that the command executed is simply mcgui/mxgui

McStas: Investigate Al.laz/Al.lau discrepancies

2

See e.g. ILL_H5 where it is used for multiple Al windows

McStas 3.1 macOS/Intel was built on macOS 12

1

(May prevent execution of the code-generator on macOS 10) Test should be carried out wrt. the other "current" McStas and McXtrace releases, plus we should decide on which releases are...

It seems build was by mistake carried out as a "mcstas 1.7".

McXtrace master test (sometimes) crash on Test_Absorption run 1

1

See http://new-nightly.mcxtrace.org/2022-03-16/McXtrace-1.x_CPU_MPICC_5e7/Test_Absorption/run_stdout_1.txt (segfault in MPI mode)

See content of http://new-nightly.mcstas.org/2022-03-18/McStas-2.x_CPU_MPICC_5e7/ILL_IN4/compile_stdout.txt "CRITICAL: User interrupt." ??

McXtrace 3.0 on MacOS Intel was distributed without GSL...

1

Workaround, in a terminal, run the commands 1) ```source /Applications/McXtrace-3.0.app/Contents/Resources/mcxtrace/3.0/miniconda3/bin/activate ``` 2) ```conda install gsl```

e.g. ``` m(c/x)plot directory/ --sweep monitorfile.mon ```

McXtrace mxplot calls mcplot-pyqtgraph when 'x' is pressed.

1

There is a hard-coded call of mcplot somewhere, needs a mccode_config based switch