micromorphic_tools

Project Description

A collection of useful tools and utilities for micromorphic continuum mechanics. These utilities are intended to reduce the implementation time of constitutive model development by providing a library of functions which are verified and ready to be implemented.

Information

• Documentation: https://aea.re-pages.lanl.gov/material-models/tardigrade_micromorphic_tools
• Wiki: https://re-git.lanl.gov/aea/material-models/tardigrade_micromorphic_tools/-/wikis/home

Developers

• Nathan Miller: nathanm@lanl.gov
• Kyle Brindley: kbrindley@lanl.gov
• Peter Schaefferkoetter: Peter.Schaefferkoetter@colorado.edu

Dependencies

Compilers

• c++11 compiler (listed version number has been tested at some point)
  • g++ >= GNU 4.8.5

Executables

• CMake >= 3.14
• Doxygen >= 1.8.5
• LaTeX >= 2017

Conda Environment

For convenience, the minimal Python environment requirements for the documentation build are included in configuration_files/environment.yaml. This file was created from the pipreqs command line tool and Sphinx configuration inspection, e.g. the extension packages.

$ pwd
path/to/tardigrade_micromorphic_tools/
$ pipreqs --use-local --print --no-pin .

A minimal anaconda environment for building the documentation can be created from an existing anaconda installation with the following commands.

$ conda env create --file configuration_files/environment.yaml

You can learn more about Anaconda Python environment creation and management in the Anaconda Documentation.

C++ Libraries

NOTE

Non-admin installations for Eigen and Boost are no longer required.** This project is built and deployed against C++ libraries managed in Conda. See the Conda environment file and README discussion for non-admin environment management.

• Eigen >= 3.3.7
• BOOST >= 1.59.0
• error_tools: https://re-git.lanl.gov/aea/material-models/tardigrade_error_tools
• vector_tools: https://re-git.lanl.gov/aea/material-models/tardigrade_vector_tools
• constitutive_tools: https://re-git.lanl.gov/aea/material-models/tardigrade_constitutive_tools

If not found on the current system or active Conda environment, all of the *_tools libraries are pulled from their git repos by branch name and built with their respective cmake files as part of the cmake build for this project.

Build and Test

This project is built with CMake and uses Sphinx to build the documentation with Doxygen + Breathe for the c++ API.

Build on sstelmo

1. Activate the correct python environment

   $ module load python/2020.07-python-3.8
   $ sv3r

2. Create a build directory

   $ pwd
   /path/to/tardigrade_micromorphic_tools/
   
   $ mkdir build
   $ cd build

3. Configure cmake3

   This step only needs to be performed once unless you need to specify a new CMake configuration for a re-build. Most command line arguments and environment variables are stored in the CMake cache. Anything found in cache will not be re-configured unless you remove the cache file or clobber the build directory.

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   $ cmake3 ..

4. Build various portions of the project

   Most of the project will re-build only as necessary after source updates. Some portions of the documentation require a make clean after documentation source file updates to force a re-build.

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   
   # Build everything
   $ cmake3 --build .
   
   # Build only the c++ primary libraries
   $ cmake3 --build src/cpp

5. Locate build files

   The build directory structure may change between version releases. Developers and users are encouraged to become familiar with the bash find, grep, and tree commands to locate build files.

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   
   # find c++ libraries and ignore intermediate files with similar extensions
   $ find . \( -name "*.o" -o -name "*.so" -o -name "*.a" \) | grep -vE "\.cpp\."

6. Clean build directory to force a re-build

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   
   $ make clean

Test on sstelmo

4. Build tests of the project

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   
   # Build c++ tests
   $ cmake3 --build src/cpp/tests

5. Run the tests

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   
   # Run ctest
   $ ctest
   
   # Results print to screen
   # View details of most recent test execution including failure messages
   $ less Testing/Temporary/LastTest.log

Building the documentation

HEALTH WARNING

The sphinx API docs are a work-in-progress. The doxygen API is much more useful.

To build just the documentation pick up the steps here:

2. Create the build directory and move there

   $ pwd
   /path/to/tardigrade_micromorphic_tools/
   $ mkdir build/
   $ cd build/

3. Run cmake3 configuration

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build/
   $ cmake3 ..

4. Build the docs

   $ cmake3 --build docs

5. Documentation builds to:

   tardigrade_micromorphic_tools/build/docs/sphinx/html/index.html

6. Display docs

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build/
   $ firefox docs/sphinx/html/index.html &

7. While the Sphinx API is still a WIP, try the doxygen API

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build/
   $ firefox docs/doxygen/html/index.html &

Install the library

Build the entire before performing the installation.

4. Build the entire project

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   $ cmake3 --build .

5. Install the library

   $ pwd
   /path/to/tardigrade_micromorphic_tools/build
   $ cmake --install . --prefix path/to/root/install
   
   # Example local user (non-admin) Linux install
   $ cmake --install . --prefix /home/$USER/.local
   
   # Example install to conda environment
   $ conda active my_env
   $ cmake --install . --prefix ${CONDA_DEFAULT_ENV}
   
   # Example install to W-13 CI/CD conda environment performed by CI/CD institutional account
   $ cmake --install . --prefix /projects/aea_compute/release

Contribution Guidelines

Git Commit Message

Begin Git commit messages with one of the following headings:

• BUG: bug fix
• DOC: documentation
• FEAT: feature
• MAINT: maintenance
• TST: tests
• REL: release
• WIP: work-in-progress

For example:

git commit -m "DOC: adds documentation for feature"

Git Branch Names

When creating branches use one of the following naming conventions. When in doubt use feature/<description>.

• bugfix/\<description>
• feature/\<description>
• release/\<description>

reStructured Text

Sphinx reads in docstrings and other special portions of the code as reStructured text. Developers should follow styles in this Sphinx style guide.

Style Guide

This project does not yet have a full style guide. Generally, wherever a style can't be inferred from surrounding code this project falls back to PEP-8-like styles. There are two notable exceptions to the notional PEP-8 fall back:

1. Doxygen style docstrings are required for automated, API from source documentation.
2. This project prefers expansive whitespace surrounding parentheses, braces, and brackets.
   • No leading space between a function and the argument list.
   • One space following an open paranthesis (, brace {, or bracket [
   • One space leading a close paranthesis ), brace }, or bracket ]

An example of the whitespace style:

my_function( arg1, { arg2, arg3 }, arg4 );

The following sed commands may be useful for updating white space, but must be used with care. The developer is recommended to use a unique git commit between each command with a corresponding review of the changes and a unit test run.

• Trailing space for open paren/brace/bracket

  sed -i 's/\([({[]\)\([^ ]\)/\1 \2/g' <list of files to update>

• Leading space for close paren/brace/bracket

  sed -i 's/\([^ ]\)\([)}\]]\)/\1 \2/g' <list of files to update>

• White space between adjacent paren/brace/bracket

  sed -i 's/\([)}\]]\)\([)}\]]\)/\1 \2/g' <list of files to update>