Merge pull request WISDEM#54 from NREL/docs

Update docs

README.md

@@ -19,6 +19,10 @@ The NREL Reference OpenSource Controller (ROSCO) provides an open, modular and f
 ## Documentation
 All relevant documentation about the ROSCO toolbox and ROSCO controller can be found at through [ROSCO's readthedocs webpage](https://rosco-toolbox.readthedocs.io/en/latest/). Here, users can find the information on [installing the ROSCO toolbox](https://rosco-toolbox.readthedocs.io/en/latest/source/install.html#installing-the-rosco-toolbox) and [compiling ROSCO](https://rosco-toolbox.readthedocs.io/en/latest/source/install.html#compiling-rosco) for control purposes. Additionally, there is information on the standard workflow and uses cases for the ROSCO toolchain, and more. 
 
+## Survey
+Please help us better understand the ROSCO user-base and how we can improve rosco through this brief survey:
+[ROSCO toolchain survey](https://forms.office.com/Pages/ResponsePage.aspx?id=fp3yoM0oVE-EQniFrufAgGWnC45k8q5Kl90RBkHijqBUN0JTNzBJT1QwMjIzNDhCWDlDTUZPWDdMWC4u)
+
 ## Referencing
 If the ROSCO Toolbox played a role in your research, please cite it. This software can be
 cited as:

docs/index.rst

@@ -20,27 +20,38 @@ Figure :numref:`fig-RT` shows the general workflow for the ROSCO toolchain.
 
 **ROSCO Toolbox**
 
-- Generic tuning of NREL's ROSCO controller
-- Simple 1-DOF turbine simulations for quick controller capability verifications
-- Parsing of OpenFAST input and output files
-- Block diagrams of these capabilities can be seen in architecture.png.
+* Generic tuning of NREL's ROSCO controller
+* Simple 1-DOF turbine simulations for quick controller capability verifications
+* Parsing of OpenFAST input and output files
+* Block diagrams of these capabilities can be seen in architecture.png.
 
 **ROSCO Controller**
 
-- Fortran based
-- Follows Bladed-style control interface
-- Modular
+* Fortran based
+* Follows Bladed-style control interface
+* Modular
 
-*Standard Use*
+Standard Use
+------------
 
 For the standard use case in OpenFAST, ROSCO will need to be compiled. This is made possible via the instructions found in :ref:`install`. Once the controller is compiled, the turbine model needs to point to the compiled binary. In OpenFAST, this is ensured by changing the :code:`DLL_FileName` parameter in the ServoDyn input file. 
 
 Additionally, an additional input file is needed for the ROSCO controller. Though the controller only needs to be compiled once, each individual turbine/controller tuning requires an input file. This input file is generically dubbed "DISCON.IN''. In OpenFAST, the :code:`DLL_InFile` parameter should be set to point to the desired input file. The ROSCO toolbox is used to automatically generate the input file. These instructions are provided in the instructions for :ref:`standard_use`.
 
-**Technical Documentation**
+Technical Documentation
+-----------------------
 A publication highlighting much of the theory behind the controller tuning and implementation methods can be found at:
 https://wes.copernicus.org/preprints/wes-2021-19/
 
+Survey
+------
+Please help us better understand the ROSCO user-base and how we can improve ROSCO through this brief survey:
+
+.. raw:: html
+
+   <iframe width="640px" height= "480px" src= "https://forms.office.com/Pages/ResponsePage.aspx?id=fp3yoM0oVE-EQniFrufAgGWnC45k8q5Kl90RBkHijqBUN0JTNzBJT1QwMjIzNDhCWDlDTUZPWDdMWC4u&embed=true" frameborder= "0" marginwidth= "0" marginheight= "0" style= "border: none; max-width:100%; max-height:100vh" allowfullscreen webkitallowfullscreen mozallowfullscreen msallowfullscreen> </iframe>
+
+|
 Directory
 ---------
 
@@ -65,5 +76,4 @@ Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
-limitations under the License.
-
+limitations under the License.