v0.13.0
What's Changed
- [Add] env variable specified component search paths by @g5t in #137
- [Ref] module global registries to reduce git reliance by @g5t in #138
- More robust use of the
Flavorenumerated value by @g5t in #140
It is now possible to specify local component, data file, and library search paths for mcstas-antlr, mcxtrace-antlr, mcrun-antlr, and mxrun-anltr through the environment variables ${MCCODEANTLR_MCSTAS__PATHS} and ${MCCODEANTLR_MCXTRACE__PATHS}.
These are likely to be most-useful if you already have, e.g., McStas installed from Conda-Forge, to avoid downloading file(s) which are already present on your system. In such a case something like the following may be useful
~$ micromamba create -n mcstas -c conda-forge mcstas mccode-antlr
~$ micromamba activate mcstas
(mcstas) ~$ export MCCODEANTLR_MCSTAS__PATHS="${MCSTAS}"
(mcstas) ~$ export MCCODEANTLR_MCCODE_POOCH__TAG="v$(mcrun --version)"
(mcstas) ~$ mcstas-antlr some.instrSetting the tag used for fetching remote content is not necessary, but should hopefully prevent any clashes if a required file is missing.
Use of some functions from within Python will require slight modification due to signature changes.
Notably, the use of Assembler will now require that the 'flavor' of the McCode language being targeted is specified as one of the enumerated Flavor values.
You can from mccode_antlr import Flavor to get access to Flavor.MCSTAS and Flavor.MCXTRACE.
Full Changelog: v0.12.0...v0.13.0