SALAMANDER Verification, Validation, and Example Cases

For software quality assurance (SQA) purposes, SALAMANDER undergoes verification, validation, and benchmarking. The SALAMANDER development team defines these terms as:

• Verification: Comparing SALAMANDER predictions against analytical solutions in different conditions, which are often simple cases.

• Validation: Comparing SALAMANDER predictions against experimental data.

• Benchmarking: Comparing SALAMANDER predictions against other codes.

Note that in addition to monitoring SALAMANDER performance and reproducibility in verification and validation cases, the effects of changes made to SALAMANDER are tracked. A series of automated tests are performed via continuous integration using CIVET to help identify any changes in SALAMANDER's predictions, therefore ensuring stability and robustness.

Example cases have also been added, independent of the SQA cases shown below, which showcase existing SALAMANDER capabilities and demonstrate potential applications. In all cases, the existing input files should allow users to leverage prior work.

Finally, for more references of SALAMANDER usage, a list of publications supporting SALAMANDER development can be found here.

SALAMANDER couples with other MOOSE-based applications, such as TMAP8 or Cardinal. These projects have their own documentation regarding SQA and examples, which can be found at the following locations:

• TMAP8 Verification and Validation

• Cardinal Tutorial

List of verification cases

List of validation cases

List of benchmarking cases

List of example cases