Issue #0: AEOS example environment

[Mark2000]

Description

AEOS example environment.

Type of change

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

How should this pull request be reviewed?

• By commit
• All changes at once

How Has This Been Tested?

Documentation builds without errors.

Future Work

Update with citation to paper.

Checklist

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation and release notes
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• If I changed an example ipynb, I have locally rebuilt the documentation

[Yume27]

Once the referenced paper is added to the example script description, it will be a great example!