All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- The
Plugin.__call__
method now accepts anoutput_dir
argument that specifies the directory created in the database (#107) - GCMAT plugin via the
PluginGCMAT
class (114)
- Fixed path to system python executable in dakota plugin
- Fixed path for templates rendered from the
extra_template_inputs
argument inPluginGeneric
and subclasses (#109) - Update to fix
PluginDakota
executable (#110)
- The
Plugin.__call__
method now supports acleanup
argument (#92) - Support for natural element expansion in
PluginMCNP
(#93, #102) - Reorganize the structure of
csv_data
generated byPluginSAS
(#98)
- Fix setting of executable for
PluginABCE
(#94)
- ACCERT plugin via the
PluginACCERT
class (#83) - Command-line tool for inspecting database (#86)
- The
PluginMCNP
class now has aninput_file
property (#88)
- All plugins now support an
executable
argument to explicitly specify the executable to be used (#75) - A
verbose
argument has been added toPlugin.__call__
that controls whether screen output is printed (#82)
- DAKOTA plugin via the
PluginDakota
class - ABCE plugin via the
PluginABCE
class - Ability to define a generic plugin via the
PluginGeneric
class - The
Database
class now has aremove
method that allows a single result to be removed
- The OpenMC plugin unit test no longer requires the
OPENMC_CROSS_SECTIONS
environment variable to be set
- RELAP-5 Plugin
- MCNP Plugin
- Serpent Plugin
- The
Plugin.__call__
method now allows arbitrary keyword arguments to be passed on to thePlugin.run
method - The
Database
class now acts like a sequence - Database directory names use random strings to avoid clashes when multiple instances of WATTS are running simultaneously
- File template-based plugins now accept an
extra_template_inputs
argument indicating extra template files that should be rendered - The
PluginOpenMC
class now takes an optionalfunction
argument that specifies an arbitrary execution sequence - All plugins consistently use an attribute
executable
for specifying the path to an executable
- Use non-blocking pipe when capturing output to avoid some plugins stalling.
- Avoid use of Unix-specific features in the Python standard library when running on Windows
- SAS4A/SASSY-1 Plugin
- Serialization/deserialization handled through dill instead of h5py
- Calling a plugin is called via the
__call__
method instead ofworkflow
- WATTS infrastructure
- OpenMC Plugin
- MOOSE Plugin
- PyARC Plugin
- initial documentation