Skip to content

Commit

Permalink
remove trailing whitespace doc for 'vision_converter'
Browse files Browse the repository at this point in the history
DCO Remediation Commit for Paul Schulz <paul@mawsonlakes.org>

I, Paul Schulz <paul@mawsonlakes.org>, hereby add my Signed-off-by to this commit: 9eea074

Signed-off-by: Paul Schulz <paul@mawsonlakes.org>
  • Loading branch information
PaulSchulz committed Sep 3, 2024
1 parent 9eea074 commit 6f05183
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/converters/vision_converter.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,20 +9,20 @@ The Vision Excel converter converts the Excel exports from Vision to PGM data fo
The default mapping of all attributes is stored in the `vision_en.yaml` and `vision_nl.yaml` files in [config](https://github.com/PowerGridModel/power-grid-model-io/tree/main/src/power_grid_model_io/config) directory.
Custom mapping files are supported via passing the file directory to the constructor of the converter.

## Load rate of elements
## Load rate of elements

Certain `elements` in Vision, i.e., appliances like transformer loads and induction motor have a result parameter of load rate.
In Vision, load rates are calculated without considering the simultaneity factors of connected nodes.
So we may observe a variation in power inflow/outflow result (i.e., P, Q and S) due to different simultaneity factors. But the load rate always corresponds to `simultaneity of loads=1`.

When we make conversion to PGM, the input data attributes of PGM for loads like `p_specified` and `q_specified` are modified as per simultaneity. The resulting loading then takes simultaneity into account.
When we make conversion to PGM, the input data attributes of PGM for loads like `p_specified` and `q_specified` are modified as per simultaneity. The resulting loading then takes simultaneity into account.
**Hence, the loading of such elements may not correspond to the load rate obtained in Vision**

## Transformer load modeling

power-grid-model-io converts the transformer load into a individual transformer and a load for usage in power-grid-model.
power-grid-model-io converts the transformer load into a individual transformer and a load for usage in power-grid-model.
To the best of our knowledge, Vision modeles a transformer load differently than an individual transformer plus load.
There is a minor difference in both the reactive power consumed and generated.
There is a minor difference in both the reactive power consumed and generated.
This might correspond to a minor voltage deviation in the results.

```{tip}
Expand All @@ -38,9 +38,9 @@ Note that in symmetrical calculations, Vision does not include clock angles of t

Some components are yet to be modeled for conversions because they might not have a straightforward mapping in power-grid-model. Those are listed here.

- power-grid-model currently does not support PV(Active Power-Voltage) bus and related corresponding features.
- power-grid-model currently does not support PV(Active Power-Voltage) bus and related corresponding features.
- Currently, the efficiency type of PVs(Photovoltaics) element is also unsupported for all types except the `100%` type. For the efficiency type: `0, 1 pu: 93 %; 1 pu: 97 %`, the generation power is multiplied by 97% as a closest approximation.
- The conversions for load behaviors of `industry`, `residential` and `business` are not yet modeled. The load behaviors usually do not create a significant difference in power-flow results for most grids when the voltage at bus is close to `1 pu`. Hence, the conversion of the mentioned load behaviors is approximated to be of `Constant Power` type for the time being.
- The conversions for load behaviors of `industry`, `residential` and `business` are not yet modeled. The load behaviors usually do not create a significant difference in power-flow results for most grids when the voltage at bus is close to `1 pu`. Hence, the conversion of the mentioned load behaviors is approximated to be of `Constant Power` type for the time being.
- The source bus in power-grid-model is mapped with a source impedance. `Sk"nom`, `R/X` and `Z0/Z1` are the attributes used in modeling source impedance. In Vision, these attributes are used only for short circuit calculations
- The load rate for transformer is calculated in Vision by current i.e., `load_rate = max(u1 * I1, u2 * I2) * sqrt(3) / Snom * 100`. Whereas in power-grid-model, loading is calculated by power, i.e., `loading = max(s1,s2)/sn`. (Note: The attribute names are as per relevant notation in Vision and PGM respectively). This gives a slight difference in load rate of transformer.
- A minor difference in results is expected since Vision uses a power mismatch in p.u. as convergence criteria whereas power-grid-model uses voltage mismatch.
Expand All @@ -52,7 +52,7 @@ Vision introduced UUID based identifier system since version 9.7. It is implemen

An examplery usage can be found in the example notebook as well as in the test cases.

## Common/Known issues related to Vision
## Common/Known issues related to Vision
So far we have the following issue known to us related to Vision exported spread sheets. We provide a solution from user perspective to the best of our knowledge.

### Duplicated `P` columns
Expand Down

0 comments on commit 6f05183

Please sign in to comment.