Conversation
…per_unit explanation for transformers
Changed accessor and getter language across multiple pages
Edits include deleting the original supplemental attributes explanation, and creating a new one. Then, adding in two how tos, which describe how to add supplemental attributes and then a second how to about querying the supplemental attributes to get additional information. Update the glossary with UUID description as well.
First edits to system explanation and a new how-to. Also edited the make.jl file to include previously committed files and these new files.
Key changes include adding @id references to the tutorials, referencing those tutorials in the explanation, and creating a separate how-to using code originally featured in the system explanation.
Successfully compiled the documentation and fixed a number of issues. Most of them were for broken or missing references.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1635 +/- ##
==========================================
+ Coverage 84.03% 84.05% +0.01%
==========================================
Files 203 203
Lines 10462 10462
==========================================
+ Hits 8792 8794 +2
+ Misses 1670 1668 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
@jbrossman I haven't taken a look yet, but FYI, about figures there's a different file path to get it to show up locally versus on github ("../" vs. "../../" or vice versa). We will want whichever one gets it to show up on the github Preview, so don't worry about it if it doesn't show up locally |
| 1. **Categorization by behavior:** Components that serve the same modeling role share a | ||
| common abstract supertype. Code can retrieve all components of a given category — all | ||
| generators, all transmission branches — without enumerating every specific technology | ||
| type. | ||
|
|
||
| 2. **Generic and extensible model logic:** Downstream packages such as | ||
| [`PowerSimulations.jl`](https://nrel-sienna.github.io/PowerSimulations.jl/stable/) | ||
| define optimization formulations against abstract types. A new concrete component type | ||
| slots into existing model formulations automatically, as long as it implements the | ||
| expected interface. This means users can define technologies not yet in the package and | ||
| have them work with existing tools. |
There was a problem hiding this comment.
[JuliaFormatter] reported by reviewdog 🐶
| 1. **Categorization by behavior:** Components that serve the same modeling role share a | |
| common abstract supertype. Code can retrieve all components of a given category — all | |
| generators, all transmission branches — without enumerating every specific technology | |
| type. | |
| 2. **Generic and extensible model logic:** Downstream packages such as | |
| [`PowerSimulations.jl`](https://nrel-sienna.github.io/PowerSimulations.jl/stable/) | |
| define optimization formulations against abstract types. A new concrete component type | |
| slots into existing model formulations automatically, as long as it implements the | |
| expected interface. This means users can define technologies not yet in the package and | |
| have them work with existing tools. | |
| 1. **Categorization by behavior:** Components that serve the same modeling role share a | |
| common abstract supertype. Code can retrieve all components of a given category — all | |
| generators, all transmission branches — without enumerating every specific technology | |
| type. | |
| 2. **Generic and extensible model logic:** Downstream packages such as | |
| [`PowerSimulations.jl`](https://nrel-sienna.github.io/PowerSimulations.jl/stable/) | |
| define optimization formulations against abstract types. A new concrete component type | |
| slots into existing model formulations automatically, as long as it implements the | |
| expected interface. This means users can define technologies not yet in the package and | |
| have them work with existing tools. |
| ``` ⠀ | ||
| For a hands-on introduction to navigating the type hierarchy, see the | ||
| [Create and Explore a Power System](@ref tutorial_creating_system) tutorial. | ||
| ``` |
There was a problem hiding this comment.
[JuliaFormatter] reported by reviewdog 🐶
| ``` | |
| ``` | |
| ``` |
| @@ -1,4 +1,4 @@ | |||
| # # Create and Explore a Power `System` | |||
| # # [Create and Explore a Power `System`](@id tutorial_creating_system) | |||
There was a problem hiding this comment.
I think these ID tags show up badly in the Jupyter notebook versions of the tutorials, so let's remove and just use the title tags if it all possible
| The system above is invalid because the bus connected to the Alta generator is not | ||
| part of subsystem "1". Add the bus first, then re-run [`from_subsystem`](@ref): | ||
|
|
||
| ```@repl subsystem |
There was a problem hiding this comment.
This doesn't fully get to an error-free resolution. Maybe at least make a comment underneath that a similar approach would be needed to resolve the remaining errors ( adding a slack bus or modifying the existing bus, adding an electric load to the subsystem)
| @@ -1,12 +1,35 @@ | |||
| # [Type Structure](@id type_structure) | |||
|
|
||
| Each infrastructure component is represented as a [`struct`](@ref S) — a composite data | ||
| type that bundles together the fields needed to describe that component. For example, an | ||
| `ACBus` carries fields for its bus number, nominal voltage, bus type, and more: |
There was a problem hiding this comment.
Add hyperlinks on all type and function names
Draft PR to address issues shown in #1504 and #1461 . Most changes occur from the supplemental attributes and system explanations. Spelling and cross reference issues were also addressed. While compiling the documentation a lot of the files were changed, but it's not clear what the change was.
One known issue still which is a figure not displaying. I will continue to work on this.
The contributing guidelines opened a link that did not work for me as well. Not sure if that is because I am a NLR employee or if the link is broken.