Extend Actuator Disk documentation

[DavidAnderegg]

Purpose

I started using actuator disks and was confused as how they are defined. This is my attempt to make the documentation a bit more clear.

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
• Maintenance update
• Other (please describe)

Testing

Checklist

• 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
• 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]

Codecov Report

Merging #304 (d0e8f01) into main (b0b6a6d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #304   +/-   ##
=======================================
  Coverage   41.98%   41.98%           
=======================================
  Files          13       13           
  Lines        4001     4001           
=======================================
  Hits         1680     1680           
  Misses       2321     2321           

Files Changed	Coverage Δ
adflow/pyADflow.py	68.94% <ø> (ø)

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

[DavidAnderegg]

I have no clue why the sphinx build fails. It works locally.

Also, when I click on the details page about that failed test, I get a 404.

[eirikurj]

This is due to RTD brownout since they are now requiring a build config file for all repos (see https://blog.readthedocs.com/migrate-configuration-v2/ for details). We are currently planning how to manage this file on the organization level, primarily to minimize our maintenance work. We plan to add this file soon, so there is no need to do anything here.