Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected very long lines in MV grid #253

Open
maltesc opened this issue Mar 13, 2018 · 4 comments
Open

Unexpected very long lines in MV grid #253

maltesc opened this issue Mar 13, 2018 · 4 comments
Labels

Comments

@maltesc
Copy link

maltesc commented Mar 13, 2018

I just saw a wrong assignment of a generator or load to a MV grid very far off (see red line in
screenshot from 2018-03-13 14-03-01.

This case is MV grid 792, Line_7920002

@maltesc maltesc added the bug label Mar 13, 2018
@nesnoj
Copy link
Member

nesnoj commented Mar 13, 2018

Thanks for reporting!
Could you please provide the geno_id?
I tried to open your DB table model_draft.corr_vis_mv_lines to get more details but got no permissions..

@maltesc
Copy link
Author

maltesc commented Mar 14, 2018

The purpose of the vis tables simply is the visualization of my results and they constantly change. However, you can have a look at my tables model_draft.corr_mv_lines_results and model_draft.corr_mv_bus_results where I store all my eDisGo results. You should have access to those now. The mentioned line appeared in result_id = 384.
The connected generator is Generator_433693.
I hope this helps a little...

@nesnoj
Copy link
Member

nesnoj commented Mar 14, 2018

Uhh, semms that there're some more lines affected:
line_bug

The geno with id = 433693 seems to be in Bavaria whereas HV/MV (id = 792) and MV/LV (id = 285975) stations are in Berlin (all data from dp v0.3.0). There seems to be an issue with the assignment of the geno to the right HV/MV station.

2 example genos:

SELECT *
  FROM supply.ego_dp_res_powerplant
  WHERE version='v0.3.0'
  AND id =in (433693, 19030);

Striking: Both genos are flagged (rea_flag) with M4_rest
@Ludee U got an idea?

@boltbeard boltbeard added the Prio1 Priority Level 1 label Jan 15, 2019
@mltja
Copy link
Member

mltja commented Mar 3, 2023

Check that an error is thrown if a generator with a too big distance is connected to the grid.

@mltja mltja removed the Prio1 Priority Level 1 label Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants