-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add DynaFlow.md Signed-off-by: lisrte <[email protected]>
- Loading branch information
Showing
7 changed files
with
272 additions
and
129 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
layout: default | ||
--- | ||
|
||
# Curves DSL | ||
The curves domain specific language allow a user to configure the curves Dynawo will export at the end of the simulation. This DSL defines the `curve` and the `curves` keywords. | ||
|
||
The `curve` keyword create a single curve for a dynamic model. One identifies a dynamic model by its ID, the same as the one used in the [Dynamic Models DSL](dynamic-models-dsl). The variable to plot is identified by its name. | ||
```groovy | ||
curve { | ||
dynamicModelId load.id | ||
variable "load_PPu" | ||
} | ||
``` | ||
|
||
If you want to plot a static variable, the `dynamicModelId` parameter has to be replaced by the `staticId` keyword and refers to an ID present in the static network. | ||
```groovy | ||
curve { | ||
staticId bus.id | ||
variable "Upu_value" | ||
} | ||
``` | ||
|
||
If you want to plot several variables of the same dynamic model, you can use the `curves` keyword that permit limiting boilerplate code in the script. | ||
``` | ||
// This: | ||
curve { | ||
dynamicModelId load.id | ||
variable "load_PPu" | ||
} | ||
curve { | ||
dynamicModelId load.id | ||
variable "load_QPu" | ||
} | ||
// is equivalent to: | ||
curves { | ||
dynamicModelId load.id | ||
variables "load_PPu", "load_QPu" | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
layout: default | ||
--- | ||
|
||
## DynaFlow configuration | ||
|
||
You need to tell powsybl where to find DynaFlow, by adding this into you configuration file: | ||
```yaml | ||
dynaflow: | ||
homeDir: /path/to/dynaflow # Directory obtained by unzipping the package, should contain "bin" | ||
debug: false | ||
``` | ||
To use DynaFlow as a default for all power flow computations, you may configure the `load-flow` | ||
module in your configuration file: | ||
```yaml | ||
load-flow: | ||
default-impl-name: "DynaFlow" | ||
``` |
Oops, something went wrong.