Gregory S. Tucker

Results 10 issues of Gregory S. Tucker

For the latest `v3.1` release available for (at least) x86_64 linux and macOS, attempting to interactively configure an instrument via `mcgui` raises a `TypeError`. ## Steps to reproduce the error...

ready for release
mcstas-2.7.1
mcstas-3.1
mcxtrace-1.7
mcxtrace-3.0

Implementing the fix proposed in #1595 (and mistakenly including part of #1593) The CMake project version information is used to build an integer valued C macro, with the exact value...

Version information _in generated C code_ could be useful to component authors wishing to make use of bleeding-edge developments without breaking backwards compatibility for older McCode versions. One way to...

Resolves #1592 by changing the return value of `metadata_table_defined` to `0` if the provided key is empty _and_ adding documentation for the metadata accessor methods. Adds a method that returns...

The `metadata_table_defined` method is not used in the McStas/McXtrace runtime; but it _could_ be used in a component to check if a specified `{component name | component instance name}:{metadata name}`...

According to a comment in #200 the `DETECTOR_OUT_3D` macro was removed sometime between McStas 2.0 and 2.1, yet it is still referenced https://github.com/search?q=repo%3AMcStasMcXtrace%2FMcCode%20detector_out_3d&type=code in multiple places _including_ syntax highlighting for...

For the [Python/ANTLR based code-generator](https://github.com/McStasMcXtrace/mccode-antlr) I bundled all `McStas` and `McXtrace` components plus the `C` runtime library files into a [separate repository](https://github.com/g5t/mccode-files) to avoid packaging/deploying the files with the module...

## Background ### `MCPL_output` By default the `MCPL_output` component uses its own component name as its output file name. https://github.com/McStasMcXtrace/McCode/blob/e56b1e3557d5ca3b3eded624a49e1ef9a22ebfff/mcstas-comps/misc/MCPL_output.comp#L93-L97 Which seems reasonable. It then specifies (in single processor mode)...

## Problem When run in 'scan' mode, `mcrun` captures `STDOUT` and `STDERR` in order to identify detector lines. https://github.com/McStasMcXtrace/McCode/blob/c725e6fcd621f1103b37b5d46c913be60df8dc1a/tools/Python/mcrun/optimisation.py#L261 For not-entirely-clear reasons, in some cases the scan can hang indefinitely...

As seen in the code generator, the property of each component representing its position along the instrument is `long` valued https://github.com/McStasMcXtrace/McCode/blob/c4c9421d630767f612703947bad4c82941220398/mcstas/src/cogen.c.in#L542 The `_getcomp_index` function finds the component which has a...