Feature/profast fin model

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,82 +1,82 @@
----
-name: Bug report
-about: Report a bug to help us improve
-title: 'Bug report'
-labels: "Type: Bug"
----
-
-<!--
-IMPORTANT NOTES
-
-Thank you for taking the time to report a bug. If you aren't certain whether an issue
-is a bug, please first open a Discussion. Before submitting, please reread your
-description to ensure that other readers can reasonably understand the issue
-you're facing and the impact on your workflow or results.
-
-This form is written in GitHub's Markdown format. For a reference on this type
-of syntax, see GitHub's documentation:
-https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
-
-This template contains guidance for your submission within the < ! - -, - - > blocks.
-These are comments in HTML syntax and will not appear in the submission.
-Be sure to use the "Preview" feature on GitHub to ensure your submission is formatted as intended.
-
-When including code snippets, please paste the text itself and wrap the code block with
-ticks (see the other character on the tilde ~ key in a US keyboard) to format it as code.
-For example, Python code should be wrapped in ticks like this:
-```python
-def a_func():
-    return 1
-
-a = 1
-b = a_func()
-print(a + b)
-```
-This is preferred over screen shots since it is searchable and others can copy/paste
-the text to run it.
--->
-
-# Add meaningful title here
-<!--
-A clear and concise description of the bug including what happened
-and what you expected to happen.
--->
-
-## How to reproduce
-<!--
-Describe how another person with no context can recreate this issue.
-It is typically very helpful to reduce the problem as much as possible
-and share a minimum working example. See the note above on including
-code as text rather than screenshots.
--->
-
-## Relevant output
-<!--
-Include any output, plots, or other means of communication here to add context to the problem.
- -->
-
-## HOPP version
-<!--
-Share your HOPP version and how you installed it. You can print the HOPP version from
-a Python REPL or script with these commands:
-```python
-import hopp
-print(hopp.__version__)
-```
- -->
-
-## System Information
-<!-- Add your information here. -->
- - OS: <e.g. Ubuntu 20.04 or macOS 10.12>
- - Python version: <Result of `python --version`>
- - Library versions
-   - Results of `pip freeze`, for example
-   - FLORIS
-   - matplotlib
-   - NREL-PySAM
-   - numpy
-   - numexpr
-   - orbit-nrel
-   - pandas
-   - scipy
-   - shapely
+---
+name: Bug report
+about: Report a bug to help us improve
+title: 'Bug report'
+labels: "Type: Bug"
+---
+
+<!--
+IMPORTANT NOTES
+
+Thank you for taking the time to report a bug. If you aren't certain whether an issue
+is a bug, please first open a Discussion. Before submitting, please reread your
+description to ensure that other readers can reasonably understand the issue
+you're facing and the impact on your workflow or results.
+
+This form is written in GitHub's Markdown format. For a reference on this type
+of syntax, see GitHub's documentation:
+https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
+
+This template contains guidance for your submission within the < ! - -, - - > blocks.
+These are comments in HTML syntax and will not appear in the submission.
+Be sure to use the "Preview" feature on GitHub to ensure your submission is formatted as intended.
+
+When including code snippets, please paste the text itself and wrap the code block with
+ticks (see the other character on the tilde ~ key in a US keyboard) to format it as code.
+For example, Python code should be wrapped in ticks like this:
+```python
+def a_func():
+    return 1
+
+a = 1
+b = a_func()
+print(a + b)
+```
+This is preferred over screen shots since it is searchable and others can copy/paste
+the text to run it.
+-->
+
+# Add meaningful title here
+<!--
+A clear and concise description of the bug including what happened
+and what you expected to happen.
+-->
+
+## How to reproduce
+<!--
+Describe how another person with no context can recreate this issue.
+It is typically very helpful to reduce the problem as much as possible
+and share a minimum working example. See the note above on including
+code as text rather than screenshots.
+-->
+
+## Relevant output
+<!--
+Include any output, plots, or other means of communication here to add context to the problem.
+ -->
+
+## HOPP version
+<!--
+Share your HOPP version and how you installed it. You can print the HOPP version from
+a Python REPL or script with these commands:
+```python
+import hopp
+print(hopp.__version__)
+```
+ -->
+
+## System Information
+<!-- Add your information here. -->
+ - OS: <e.g. Ubuntu 20.04 or macOS 10.12>
+ - Python version: <Result of `python --version`>
+ - Library versions
+   - Results of `pip freeze`, for example
+   - FLORIS
+   - matplotlib
+   - NREL-PySAM
+   - numpy
+   - numexpr
+   - orbit-nrel
+   - pandas
+   - scipy
+   - shapely

.github/ISSUE_TEMPLATE/config.yaml

@@ -1,5 +1,5 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Usage question
-    url: https://github.com/NREL/hopp/discussions
-    about: Have any questions about using HOPP? Post in Discussions to engage with the NREL team and HOPP community.
+blank_issues_enabled: false
+contact_links:
+  - name: Usage question
+    url: https://github.com/NREL/hopp/discussions
+    about: Have any questions about using HOPP? Post in Discussions to engage with the NREL team and HOPP community.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,57 +1,57 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: 'Feature request'
-labels: 'Type: Enhancement'
----
-
-<!--
-IMPORTANT NOTES
-
-Thank you for taking the time to suggest a feature. Before submitting,
-please reread your description to ensure that other readers can reasonably
-understand the motivation and proposed solution.
-
-This form is written in GitHub's Markdown format. For a reference on this type
-of syntax, see GitHub's documentation:
-https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
-
-This template contains guidance for your submission within the < ! - -, - - > blocks.
-These are comments in HTML syntax and will not appear in the submission.
-Be sure to use the "Preview" feature on GitHub to ensure your submission is formatted as intended.
-
-When including code snippets, please paste the text itself and wrap the code block with
-ticks (see the other character on the tilde ~ key in a US keyboard) to format it as code.
-For example, Python code should be wrapped in ticks like this:
-```python
-def a_func():
-    return 1
-
-a = 1
-b = a_func()
-print(a + b)
-```
-This is preferred over screen shots since it is searchable and others can copy/paste
-the text to run it.
--->
-
-# Add meaningful title here
-<!--
-High level description of the feature request including motivation and background.
--->
-
-## Proposed solution
-<!--
-Here's an opportunity to prototype a feature. Please include pseudocode, images, or
-any other visual aids to communicate the idea.
--->
-
-## Alternatives considered
-<!--
-Describe workarounds or alternatives even if hacky or incomplete.
--->
-
-## Additional context
-<!--
-Optional. Provide anything else that helps to communicate the idea here.
--->
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Feature request'
+labels: 'Type: Enhancement'
+---
+
+<!--
+IMPORTANT NOTES
+
+Thank you for taking the time to suggest a feature. Before submitting,
+please reread your description to ensure that other readers can reasonably
+understand the motivation and proposed solution.
+
+This form is written in GitHub's Markdown format. For a reference on this type
+of syntax, see GitHub's documentation:
+https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
+
+This template contains guidance for your submission within the < ! - -, - - > blocks.
+These are comments in HTML syntax and will not appear in the submission.
+Be sure to use the "Preview" feature on GitHub to ensure your submission is formatted as intended.
+
+When including code snippets, please paste the text itself and wrap the code block with
+ticks (see the other character on the tilde ~ key in a US keyboard) to format it as code.
+For example, Python code should be wrapped in ticks like this:
+```python
+def a_func():
+    return 1
+
+a = 1
+b = a_func()
+print(a + b)
+```
+This is preferred over screen shots since it is searchable and others can copy/paste
+the text to run it.
+-->
+
+# Add meaningful title here
+<!--
+High level description of the feature request including motivation and background.
+-->
+
+## Proposed solution
+<!--
+Here's an opportunity to prototype a feature. Please include pseudocode, images, or
+any other visual aids to communicate the idea.
+-->
+
+## Alternatives considered
+<!--
+Describe workarounds or alternatives even if hacky or incomplete.
+-->
+
+## Additional context
+<!--
+Optional. Provide anything else that helps to communicate the idea here.
+-->