LIVVkit/LIVVkit: LIVVkit 3.0.0

We are pleased to present LIVVkit v3.0.0 LIVVkit is a python-based toolkit for verification and validation of Ice Sheet Models. It aims to provide the following capabilities: Model V&V Numerical verification -- "Are we solving the equations correctly?" Physical validation -- "Are...

Full description

Bibliographic Details
Main Authors: Kennedy, Joseph H, Bennett, Andrew, Evans, Kate, Stephenprice, Ranken, Doug, Norman, Matt, Fyke, Jeremy, Hoffman, Matt, Lipscomb, William, Kelleher, Mike
Format: Article in Journal/Newspaper
Language:unknown
Published: Zenodo 2020
Subjects:
Online Access:https://dx.doi.org/10.5281/zenodo.3597497
https://zenodo.org/record/3597497
Description
Summary:We are pleased to present LIVVkit v3.0.0 LIVVkit is a python-based toolkit for verification and validation of Ice Sheet Models. It aims to provide the following capabilities: Model V&V Numerical verification -- "Are we solving the equations correctly?" Physical validation -- "Are we using the right physics?" Software V&V Code verification -- "did we build what we wanted?" Performance validation -- "did we build what the users wanted?" You can view the latest documentation here. Changelog: 3.0.0 release: Drops python 2 support -- -- commitment to supporting latest 3 python versions (currently python 3.6--3.8) More control over multiprocessing pool including the ability to not use multiprocessing (serial option) LIVVkit Elements have been moved from a basic dictionary to a class representation: elements have multiple _repr_* methods defined to produce a JSON, HTML, or LaTeX representation of the element when writing the report _repr_* methods use jinja2 templates that are defined by an instances _*_template attribute/property and so can be customized on a per-instance basis (!) instead of globally table elements support Pandas DataFrames References can be defined in a Bibtex file and will display on the analysis report page Significantly reduced the amount of custom JavaScript used to display the HTML report. Clean up of the documentation Output website no longer requires explicitly writing index.html in the page URLs Lots of community improvements such as a code of conduct, issue and PR templates, etc