Specified tolerances in assert_allclose calls

[sseraj]

Purpose

After updating the latest NumPy version to 1.25.2 (mdolab/docker#233), some of the tests fail marginally on Azure (see logs here).

The problem is that some of the assert_allclose calls are using the default atol=0 and there are some values in the arrays that are not exactly zero but less than 1e-15. I added atol=1e-15 to these calls to fix this. I also added rtol=1e-7, which is the default, for clarity.

Expected time until merged

Type of change

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (non-backwards-compatible fix or feature)
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no API changes)
• [ ] Documentation update
• [x] Maintenance update
• [ ] Other (please describe)

Testing

Current tests should pass on Azure

Checklist

• [x] I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• [ ] I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• [x] I have run unit and regression tests which pass locally with my changes
• [ ] I have added new tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation

[codecov[bot]]

Codecov Report

Merging #60 (ff83296) into main (4cba2aa) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   52.53%   52.53%           
=======================================
  Files           5        5           
  Lines        1616     1616           
=======================================
  Hits          849      849           
  Misses        767      767           

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more