References
- C. PERMANN et al., “MOOSE: Enabling Massively Parallel Multiphysics Simulation,” SoftwareX, 11, 100430 (2020); https://doi.org/10.1016/j.softx.2020.100430.
- J. D. HALES et al., “Asymptotic Expansion Homogenization for Multiscale Nuclear Fuel Analysis,” Comput. Mater. Sci., 99, 290 (2015); https://doi.org/10.1016/j.commatsci.2014.12.039.
- Y. WANG et al., “Rattlesnake User Manual,” INL/ext-15-37337, Idaho National Laboratory (2016).
- M. CACACE and A. B. JACQUEY, “Flexible Parallel Implicit Modelling of Coupled Thermal-Hydraulic-Mechanical Processes in Fractured Rocks,” Solid Earth, 8, 5, 921 (2017); https://doi.org/10.5194/se-8-921-2017.
- R. WILLIAMSON et al., “Multidimensional Multiphysics Simulation of Nuclear Fuel Behavior,” J. Nucl. Mater., 423, 1, 149 (2012); https://doi.org/10.1016/j.jnucmat.2012.01.012.
- A. SLAUGHTER et al., “Continuous Integration for Concurrent MOOSE Framework and Application Development on GitHub,” J. Open Res. Software, 3, 1, Article e14 (2015); https://doi.org/10.5334/jors.bx.
- ASME NQA-1-2008 with the NQA-1a-2009 Addenda: Quality Assurance Requirements for Nuclear Facility Applications, 1st ed., American Society of Mechanical Engineers (2009).
- D. R. GASTON et al., “Continuous Integration for Concurrent Computational Framework and Application Development,” J. Open Res. Software, 2, 1, Article e10 (2014); https://doi.org/10.5334/jors.as.
- “Django,” Django Software Foundation; https://djangoproject.com ( current as of May 13, 2020).
- “A Successful Git Branching Model,” Thoughts and Writings by Vincent Driessen (2010); https://nvie.com/posts/a-successful-git-branching-model ( current as of May 13, 2020).
- O. GOLOWINSKI, “How Merge Trains Keep Your Master Green,” GitLab Docs; https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains (current as of May 13, 2020).
- “gitworkflows—An Overview of Recommended Workflows with Git,” git; https://git-scm.com/docs/gitworkflows ( current as of May 13, 2020).
- E. HOLSCHER et al., “Docs as Code” https://www.writethedocs.org/guide/docs-as-code ( current as of May 13, 2020).
- D. VAN HEESCH, “Doxygen” (2018); https://www.doxygen.nl (current as of May 13, 2020).
- G. BRANDL and SPHINX TEAM, “Sphinx: Python Documentation Generator” (2020); https://www.sphinx-doc.org (current as of May 13, 2020).
- T. CHRISTIE, “MkDocs: Project Documentation with Markdown” (2014); https://www.mkdocs.org (current as of May 13, 2020).
- “LiveReload” GitHub (2020); https://github.com/lepture/python-livereload (current as of May 13, 2020).
- “PyYAML”; https://pyyaml.org/wiki/PyYAMLDocumentation ( current as of May 13, 2020).
- “Collaborative Data Science,” P. T. Inc. (2015); https://plot.ly (current as of May 13, 2020).
- PANDAS DEVELOPMENT TEAM, “Pandas-dev/pandas: Pandas” (2020); https://doi.org/10.5281/zenodo.3509134 ( current as of May 13, 2020).
- “Pybtex”; https://pybtex.org (current as of May 13, 2020).
- “IEEE Guide for Software Requirements Specifications,” IEEE Std 830-1998, pp. 1–26, Institute of Electrical and Electronics Engineers (1998).
- “IEEE Recommended Practice for Software Design Descriptions,” IEEE Std 1016-1998, pp. 1–23, Institute of Electrical and Electronics Engineers (1998).
- “IEEE Standard for Software Test Documentation,” IEEE Std 829-1998, pp. 1–64, Institute of Electrical and Electronics Engineers (1998).