…vity resolved.

Description

Addresses # (issue)

Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context. List any dependencies that are required
for this change. Please see CONTRIBUTING.md for more guidelines.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality
  to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce.

Test configuration

• Operating system: [e.g., Hal]
• Compiler, version number: [e.g., Python 3.X, gcc version X.X]
• Any details about your local setup that are relevant

Checklist:

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