Memory Error/Extrapolation bug

[ljlamarche]

Description

This is a draft PR to make it easier to track some of the issues/changes pertinent to #115. The main problem was a variety of memory errors that seemed to occur somewhat randomly when an Apex object was initialized, but there seem to be several things that potentially could contribute to this. (See #115 for ongoing discussion - will copy main points to this thread when ready to review).

Note: This PR should replace #116

Fixes #115 (not yet)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Confirm that short example scripts can be run.
• Check that the fortran test program compiles and generates the correct output.
• Standard unit tests

Test Configuration

• Operating system: MacOS 12.6.1 M1
• Python version number: 3.10.9
• Compiler with version number: gfortran 12.2.0

Checklist

• [x] Make sure you are merging into the develop (not main) branch
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] Add a note to Changelog.rst, summarising the changes
• [x] Add yourself to AUTHORS.rst and .zenodo.json

[ljlamarche]

Of the tests that are sill failing, one I believe will be fixed by https://github.com/aburrell/apexpy/pull/118/commits/5f0fdf884d287c5ba521b6652925bdb9f6f19370 and https://github.com/aburrell/apexpy/pull/118/commits/ed033f2081f9a94e3898dea1793a6f35c0f92b38, and the other two are related to #113, which is a separate and relatively isolated issue.