Ncrystal

Latest version: v4.1.6

Safety actively analyzes 723683 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 14

2.4.80

* RC1 for incoming release v2.5.0.

2.4.0

* Properly support delivery of NCMAT data files from plugins. For clarity,
and to avoid name clashes, such data files must follow a clear naming
scheme "ncplugin-<PLUGINNAME>_*.ncmat". The mechanism for making the
data files available will depend on how the plugin is used, and is of
course automatic. For a static plugin, built into a given NCrystal
installation, the data file will be installed along with all of
NCrystal's own data files (either as physical files or compiled into the
NCrystal library, depending on the NCrystal configuration). For a
dynamic plugin, built separately and later loaded by adding the plugin's
shared library to NCRYSTAL_PLUGIN_LIST, the data file will be compiled
into the plugin library. Finally, for plugin developers, the data files
will be made available via a symlink, ensuring that it is possible to
directly edit the data file during development.
* Support (on unix) relative paths in NCRYSTAL_PLUGIN_LIST.
* Add option to ncrystal_ncmat2cpp for injecting include statements in
generated code.
* Plugin developers can now also see their test .ncmat files in the list
provided by ncrystal_inspectfile --browse.
* Export more information to client cmake projects.

2.3.1

* Small bugfix fixing the loading of dynamic plugins.
* Ensure plugins are loaded before file searching is carried out. This
allows plugins to register in-memory files.

2.3.0

* Replace span class with a fully home-grown solution. This means that all
core NCrystal code is once more fully available under the primary
license (the Apache 2.0 license).
* Cfg parameters scatfactory and absnfactory now supports exclusion of
specific named factories. This is used to (by default) exclude current
factory from consideration when globalCreateScatter/Absorption is
invoked from a factory (github issue 51).
* Replace the '$(ncrystal-config --setup)' idiom with one which works also
when entries in PATH contains spaces: 'eval $(ncrystal-config --setup)'
(github isse 52).
* Rename internal radius variable in McStas sample, to avoid clashes with
component parameter (apparently this gave issues for McStas 3.0).

2.2.2

* Bugfix for system-wide installations. Input files were
accidentally opened in RW mode rather than just readonly, causing
permission errors when user invoking NCrystal did not have
write-permission to the input file. Thanks to the McStas crew for
noticing this.

2.2.1

* Bugfix restoring support for .nxs/.laz/.lau files which was accidentally
disabled in v2.2.0.
* Modify CMake code slightly to avoid warnings or unset CMAKE_BUILD_TYPE
under certain conditions where NCrystal is included as a sub-project.

Page 9 of 14

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.