sandy 0.9

New Features

SANDY officially switches from branch-oriented development to release-oriented development!

Historically the development of SANDY was implemented on two major branches: master and develop.

• The master branch is a legacy version with the original goal of producing perturbed nuclear data files using the command line interface (CLI).
• The develop branch sets its target to produce the perturbed nuclear data files using a API (with an extensive interface to pandas) rather than the CLI.

In parallel, the code was completely restructured from functional programming to OOP (object-oriented programming) to:

• provide users and developers more flexibility;
• implement unit testing;
• improve code clarity, readibility and maintainability.

The development of the API also extended the purpose of the code from merely producing perturbed nuclear data files to four development blocks:

• interface to nuclear data files in ENDF-6 format;
• interface to the nuclear data processing tool NJOY;
• interface to MCNP output files mctal and mshtal;
• interface to ALEPH-2 output files.

Restructuring the code brought more (reliable/unit tested) features, however, the correct run of some of the key code production processes — the sample generation pipeline — cannot be guaranteed anymore (for this, we suggest using release sandy-master). This drawback, as well as a more streamlined code installation in both Linux and Windows without fortran dependencies, will be tackled in the next release 1.0.

Contributors

@luca-fiorito-11
@AitorBengoechea
@EnricaBelfiore
@GrimFe
@Lindt8
@nicoloabrate
@promojar
@rayanhaddad169