You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the Jupyter-Notebooks using the new Python Interface (see #22 ) take multiple minutes for a full run-through, which causes the test pipeline to run quite long. This table aims to summarize the current run times (using the notebooks in #22 ) for evaluation and adaption of simulation run times and pipeline tests. The full notebook runtime is measured in a single run of pytest --durations=0 -v , the simulation run times are measured using the iPython %%timeit cell magic with the time calculated as the average over seven runs. Simulation run times contain the full setup and run of the dynamic simulation without PowerFlow or later data evaluation / plotting. Please note that this is not meant as a complete, accurate benchmark but rather as an overview over which notebooks should be tweaked when tested in the CI-pipeline.
Overall
61 notebooks in Circuits, Components or Grids 7 notebooks skipped in pytest(11,5%) 25 notebooks with asserts (41,0%)
Circuit-Examples
Full pytest-run in 760.53s (0:12:40)
26 passed, 2 skipped (92.9% tested)
10 of 28 notebooks with asserts (35,7%)
Notebook contains no error, so test could be enabled
CS_R2CL print_attributes
2.79s
12.5 µs (EMT), 12.5 µs (DP)
-
Notebook exists to show off attribute print functions, so comparisons with SL got stripped
CS_R2CL
3.36s
11.8 µs (EMT), 11.4 µs (DP)
EMT vs SL, DP vs SL
DP_Slack_PiLine_PQLoad_with_PF_Init
2.49s
71.6 µs
-
Plots currently plot the wrong time interval
DP_Slack_PiLine_VSI_Ramp
26.20s
-
-
Notebook does not use dpsimpy, plot labels are in german
DP_Slack_PiLine_VSI_with_PF_Init
47.27s
45.8s
-
wrong time interval plotted, plot labels in german
DP_SP_SynGenTrStab_3Bus_Fault
32.01s
8.94s (DP), 8.52s (SP)
-
DP_SP_SynGenTrStab_3Bus_SteadyState
12.71s
2.28s (DP), 2.11s (SP)
-
DP_SP_SynGenTrStab_SMIB_Fault
17.57s
4.06s (DP), 4.11s (SP)
-
DP_SP_SynGenTrStab_SMIB_SteadyState
12.29s
1.70s (DP), 1.45s (SP)
-
EMT_DP_Slack_PiLine_VSI_ Control_OnOff
34.25s
10.4s (EMT, control on), 11.2s (EMT, control off), 5.04s (DP, control on), 4.71s (DP, control off)
-
EMT_DP_SP_Slack_PiLine_VSI
107.11s
11.1s (EMT), 48s (DP), 47.6s (SP)
-
EMT_DP_VS_Init
3.12s
49.2ms (DP, set params), 88ms (EMT, set params), 45.1ms (DP, set attribute), 74.6ms (EMT, set attribute), 40.7ms (DP, set from node), 83.8ms (EMT, set from node)
Some of the Jupyter-Notebooks using the new Python Interface (see #22 ) take multiple minutes for a full run-through, which causes the test pipeline to run quite long. This table aims to summarize the current run times (using the notebooks in #22 ) for evaluation and adaption of simulation run times and pipeline tests. The full notebook runtime is measured in a single run of
pytest --durations=0 -v
, the simulation run times are measured using the iPython%%timeit
cell magic with the time calculated as the average over seven runs. Simulation run times contain the full setup and run of the dynamic simulation without PowerFlow or later data evaluation / plotting. Please note that this is not meant as a complete, accurate benchmark but rather as an overview over which notebooks should be tweaked when tested in the CI-pipeline.Overall
61 notebooks in Circuits, Components or Grids
7 notebooks skipped in
pytest
(11,5%)25 notebooks with asserts (41,0%)
Circuit-Examples
Full
pytest
-run in 760.53s (0:12:40)26 passed, 2 skipped (92.9% tested)
10 of 28 notebooks with asserts (35,7%)
Component examples
Full
pytest
-run in 133.57s (0:02:13)10 passed, 1 skipped (92.9% tested)
7 of 11 notebooks with asserts (63,6%)
Grid examples
Full
pytest
-run in 223.14s (0:03:43)18 passed, 4 skipped (81,8% tested)
8 of 22 notebooks with asserts (36,4%)
The text was updated successfully, but these errors were encountered: