McCode
McCode copied to clipboard
McStasMcXtrace
The home of the McStas (neutrons) and McXtrace (x-rays) Monte-Carlo ray-tracing instrument simulation codes.
- plus ensure atomic access within TRACE. E.g. W_psd_monitor has statically declared arrays.
See http://new-nightly.mcxtrace.org/2022-02-27/overview.html Zero intensity on multiple monitors, further issues on GPU than CPU. Initial investigations point in the direction of read-table_lib, especially re-used and re-binned tables, looks to be material-dependent....
Hi there, A hopefully very easy to implement but potentially very useful feature would be to have the MCCODE_VERSION available as an easily comparable integer. This will make life a...
Currently they are presented as mcdisplay.pl which will only be installed if on opts for the "full" perl tool set. (the other ones are readily available in the cmdline package)
- i.e. mention needed USERVARS in the instrumentfile + point to Test_TasReso.instr as example
The components have different structs with same name. Fixed on mccode-3 and mcxtrace-3.0-release branches: https://github.com/McStasMcXtrace/McCode/commit/879e854b29c2adfb5bae63e816446e0a78ccc9ba If needed, update your local Single_crystal by this one: [Single_crystal.comp.txt](https://github.com/McStasMcXtrace/McCode/files/8033397/Single_crystal.comp.txt) (https://github.com/McStasMcXtrace/McCode/blob/mccode-3/mcxtrace-comps/samples/PowderN.comp)
Clash with a local conda environment of the user can cause yaml / pyqtgraph / Qt related issues
Metadata
Owner
Metadata
The home of the McStas (neutrons) and McXtrace (x-rays) Monte-Carlo ray-tracing instrument simulation codes.