McCode icon indicating copy to clipboard operation
McCode copied to clipboard

The home of the McStas (neutrons) and McXtrace (x-rays) Monte-Carlo ray-tracing instrument simulation codes.

Results 223 McCode issues
Sort by recently updated
recently updated
newest added

Edited a "user config" on Windows via `mcrun --write-user-config` to allow running a specific web-browser. Surprisingly mcgui/mcrun seems to pick up that a "local" configuration is added, but this is...

Hi, there is an issue with the GUI not running both from shortcut and the shell. C:\Users\user>mcgui Traceback (most recent call last): File "C:\mcstas-3.4\lib\tools\Python\mcgui\mcgui.py", line 15, in from PyQt5 import...

When performing a mcrun scan (e.g. mcrun -c ILL_SALSA.instr mono_rock=-4,4 -N9) on an instrument containing a Monitor_nD instance without "axes", i.e. `options = "per cm2, capture, slit",` Makes the mcsimdetectors()...

workaround
mcxtrace-3.2
mcstas-3.4

Currently, mcgui and mcrun are shipped with the special default `"auto"` for the number of cores to run on. (which internally means to run mpirun _without_ specifying `-np #`) This...

ready for release
workaround
mcstas-2.7.2
mcxtrace-1.7.1
mcxtrace-3.2
mcstas-3.4

A (quick+dirty bash-) tool has been written to investigate our level of "example-documentation" for the components of McStas and McXtrace (compmatrix.sh in mcstas-comps/ and mcxtrace-comps/). Sasmodels and obsolete are disregarded...

It would be nice with these additions / improved features for mcdoc / mxdoc: Comp docs: * Automatic example search / link - dynamically list example instrs that includes the...

It would be nice with these additions / improved features for mcrun / mxrun: * Honouring `CFLAGS` and `LDFLAGS` from surrounding environment * A commandline-switch for further CFLAGS, e.g. `--CFLAGS="enable...

A profiling of the code should be performed with e.g. `gprof` and `gcov`. The procedure is the following. Then look at ways to either reduce the number of calls, or...

enhancement
C: McCode kernel

It would be nice to define a template to more naturally ensure we get the bits and pieces of information often lacking in the first bug-reporting, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository